Search options (Page 2 of 9)

I tried the same trick with %T the other day too without luck ;-)

Maybe it would be possible for Rémi to enhance %T{}
to allow calculating sub-expressions like:      >>> %T{  (%pa

EDIT:
was cut...

>>> %T{  (%pa"Numfiles.txt")  } <<<

>>> "I like it already. Will test it this days......"

Oh, it is not provided for download yet.  OK, fine.

>>> "Give me your thoughts, "
was meant based on the picture then?
What can I say? Looks nice, good, nifty.
But what means "Preference"? This is an kind of expression too, isn't it?
By preference I first thought on settings from the Options dialog (Preferences).

And BTW, I would suggest to show an kind of indicator at least, that the Preferences
are not in default state anymore, but modified by user.
Smtg like: "Preferences: default"  // "Preferences: modified !"
Or just show an star * somewhere, as text editors do on modified documents.

I will take another look later, maybe I see smtg more....

Good work, Rémi !

EDIT:
>>>> "For this example the preferences contains a rule to replace "@" with "o"."

AHHH, NOW I see it

OK, I have read it before, but not understood, because I though in that row the new path\ is the main point.

All clear now.

Wow, that alone seems to be a great help :thumpsup:

I remembering scrolling the long list to find the wanted,...
and now just enter 'date' e.g., and you get filtered what you want. Great!

Probably an idea for the Expression testbed (which deserves a icon on the right of the Expression box in the main window, btw)

Me think, there is nothing much won, if the Variables are listed in tabs or as a tree view.

My improvement ideas:

1) remember the last use tab (e.g. 'Exif'), best as an optional setting.

2) implement a search box (edit control) to filter the list.
Now a tree view would make sense, to see all e.g. 'date' related variables, no matter if from 'Base' or 'Exif' or else.

3) make that window dock-able to have it open all the time, without disturbing the view on the main app.

| Explorer       |       File list       |
|                     |                        |
|                     |                        |
|                     |                        |
|                     |                        |
|         Completion                   |
|                                            |
|                                            |

4) some work for you, but maybe an idea:

add an column for basic explanations, like:

Base:
%T{""} | Text file line | %T{"C:\\fr.txt",2}

Modifiers:
(p,n) | Substring | %b(1,8)
(s/e/f/m) | Regular Expression | %b(s/exp/replace/mod)
(tr/f/t/m) | Transliteration | %b(tr/search list/replace list/mod)

But maybe that is too much information presented.
And there is also the Help link in context menu.

Glad you like it.

If you are going to elevate this "%n{ p, s, i, r }" syntax
to GUI level on "File > Preferences > Numbers",
you maybe want to add also "%nr" for this
as an shortcut of "%n{<default>,<default>,<default>,<default>}"
which use the setting from that GUI dialog? Just an idea!

Ahh, %np and %nc should not inherit this "r" setting.
They still use p,s,i only.
Or do the user have to think about resetting the "r" to zero?

I think I have to deploy a sketch

- - -

Rémi wrote:
The reset associated to the variable (path, name etc.) will take over this new one, right ?

Sorry, I do not understood how around you mean this.

I guess you mean some variable (%np/%nc or %nr) will win an conflict if both are applied by user?
I also think this is too complex for me and over my scope ;-)

Lets see:

I think this GroupNumbering "r" will be mostly the last one?

We can use %np on same path .... and then %n{ , , , r=2}
C:\temp\fileA 1 - 1
C:\temp\fileB 2 - 2
C:\temp\fileC 3 - 1
C:\temp\fileD 4 - 2
C:\temp\fileE 5 - 1
C:\temp\fileF 6 - 2

We can use %nc on same name .... and then %n{ , , , r=2}
C:\temp\fileA 1 - 1
C:\temp\fileA 2 - 2
C:\temp\fileA 3 - 1
C:\temp\fileA 4 - 2
C:\temp\fileA 5 - 1
C:\temp\fileA 6 - 2

Sorry if I am not of an use here.
But will try to support you if I get the direction.
And I need a lot of time to get around this.

Hi Rémi,

Lua seems logical for a cross-plattform scripting language, beside of Python.

Unfortunately I have never worked with it  (only with VBS, JS, PascalScript, PowerShell, AutoHotkey)
So I can't say anything about that. But it looks good, as most other language, based on the documentation.

If you not already know, there is http://rosettacode.org/wiki/Category:Lua
with comparison to other languages for a quick overview.

All the best to you.

Today I get it.
>>Siren tracks the modifications done to its current directory by other programs

You don't mean own modifications by renaming, but really modifications by other programs?

I think, own modifications should be seen immediately.
For modifications done by other programs it would be enough *for me* to just press F5 from time to time. (on Win32)

But maybe, since you have the code already, just make it optional in the settings and disable it on default.

? Did I really have missed this post? Sorry for late responce ;-)

Looks fine. Good idea.

-------------------------------------------------------

While touching about an use, I was thinking about a folder full of MP3s and one or more album cover JPGs.
This new filter will allow me to rename e.g. the JPGs by the parent folder name, without utilizing the Filter combobox by hand.
[*.jpg]%p%ncs.%e

Add timestamp to filename; with exif date for jpg and file creation date for mp4:
[*.jpg]%Xdo_%f;[*.MP4]%dc_%f

Explanations for other readers:
[*.jpg] work only on JPG files (not implemented yet)
%p   parent directory
%n   the selection number
%nc  the selection number relative to a name "collision"
%ncs same principle as "%nc" except that it is empty for the first element of the "collision group" and prefixed by a "_" for the others.
%Xdo EXIF DateTimeOriginal
%dc the creation date and time

-------------------------------------------------------

Ideas:

- first I thought, why not dropping the leading "*." part, it is superfluous, and maybe use a space as seperator,
like just [jpg nef png] instead of [*.jpg;*.nef;*.png]
But your origin idea fits better along with the command line "/S" parameter.

- invent filetype groups to use as filter: [Image] = png jpg jpeg bmp, [Video] = avi mpeg , [Audio] = wav mid mp3
[Image]Photo_%f;[Video]Video_%f

- Will this work: exif date for jpg, creation date for ALL *.* others (but NOT for jpgs)
[*.jpg]%Xdo_%f;[*.*]%dc_%f

-------------------------------------------------------

Will you expand this filter feature in future? 

Just see if the expression inside the [ ] can evaluated to true.

[JPG && (%Ix -lt 100 || %Iy -lt 80)]thumbnail_%f
[%N]_numberfound_%f

-------------------------------------------------------

Hi and welcome!

>>(I wish there were more examples)
>>If someone can explain why this doesn't work that would be great: 

Some tips:

1) RegEx is a pattern matching system to take some parts to keep and maybe some others to drop.
So one would e.g. match parts of the file name, store them in backreference groups and reorder them in the output.
As you did. But there is no magic as conjure up additional parts out of nowhere.

There is no such things as "padding" per se. Just matching parts and use them for some operations. As Rémi did with his
first additional expression s/-(\d)-/-0\1-/g (match single digit between hyphens and replace with '0' and matched digit)
Then you can continue whit that first output as input for the reorder-expression of you.

2) Parentheses () can be used to store what is matched for later reuse by \1 and so on.
Those backreference groups are counted from left to right.
So s/([0-9]+)-([0-9]+)-([0-9]+ will provide three backreference groups,... but you use *four* references \3-\2-\1 \4
The \4 is to much, because not matched, and not needed either as Siren provide the unmatched part on its own.

3) Instead of [0-9] you can use the shorter \d
The character class [0-9] would be used as e.g. [1-3] to match 1,2 or 3 only.
But to match any digit out of 0,1,2,3...9 you can use just \d

So your expression could be written as s/(\d+)-(\d+)-(\d+)/\3-\2-\1

That you do not need to match the text too is because which regex engine is used,
and how Rémi has implemented that.

HTH?

> hide the visualization window from the main View menu.

build_954 on Win7 64-bit:

- I can hide or show it left or right.
- It remembers its size after hiding.
- The settings (hide and size) are remembered after an restart of Siren

Fine.