Search options (Page 4 of 12)

Hello,

An expression like this one might do it :
%b[-1]@%nc@%f;%f[3,"@"]_%f[2,"@"]

Using the name itself looks weird but it works well (for now).
Your idea is very interesting but maybe overkill.

Thanks for all your suggestions

It seems that the selection number reseting variables, %np and %nc, can use this new feature too.

For example for "%np" :

%b_%np{,,,2}.%e

C:\A\a_001.txt
C:\A\b_002.txt
C:\A\c_001.txt => reset due to maximum reached
C:\B\d_001.txt => reset due to directory change
C:\B\e_002.txt

This looks wrong for name collision, %nc, because a reset would generate a collision ...
but why blocking the user if that's what he wants and knows that the final new name won't create any
problem.

Maybe does this need more brain juice.

Hello Stefan,

It's nice to hear from you.
Even if I have not spent as much time on Siren as I would have liked, the work continues (will it ever end ?).
The "Expression filters" feature has been implemented. The only missing element is an explained example.
Many other smaller new things, bug fixes and improvements should be part of the next version.
The tests will require a lot of efforts and I tend to postpone the task by implementing other changes.

The next feature I will maybe add to the release after the next is allowing the user to create its own variables and associate code to them. It would written in a scripting language.
The one that looks interesting is Lua. Please, give me your ideas about this.

I hope that everything goes well for you.

Thanks again for your interest in this little project.

Best regards,

Remi

Siren doesn't have a "search for file" expression function.
What I imagined was that, while in "tree mode", the first selected file of each sub-folder could be the naming source.
This selection would have to be done manually or with other selection options.
This feature is not present yet and would need work to be correctly implemented.

Hello,

This is an interesting question.
I may have an idea to achieve it but it needs some code modifications.
I'll try to add it in a new release.

Thanks

Hello Stefan,

Thanks a lot for your feedback.

I would like to keep the "file filter" notion consistent all accros Siren : command line, filter combobox, search/selection filter ...

Maybe, but not for the first version.

No. If a file passes a filter (an empty filter is equivalent to "*.*" or "*") then the sub-expression is applied to it.
This can solved with unperfect workarounds like :
[*.jpg]@%Xdo_%f;[[!@]*]@%dc_%f;%f(2)
or
[*.jpg]%Xdo_%f;[*.[!j]??;*.?[!p]?;*.??[!g]]%dc_%f

Why not. It depends on the users needs (and I am part of them) and my available work time for it.

Just another relatively important change that I would like to do : the removal of the disk change monitoring feature.
Siren 3.14 tracks the modifications done to its current directory by other programs and reflect the changes in its file list.
This feature can be handy but it is heavy, sometimes not reliable and doesn't work in some cases.
What is your opinion about this step backwards ?

Hello,

I imagine that you are using the last version of Siren, the 3.14.
This version includes a new feature : the directory monitoring.
This monitoring goes as far that it handles the modifications done by Siren itself : renaming, copying etc.
Unfortunately this version of the monitoring module has issues under Windows. The GNU/Linux one seems ok.
One of the indirect signs of the problem is the one you have noticed : the status bar is not correctly updated.
I don't think the rename/copy operations are affected and a directory refresh should show it.   

Work on Siren 3.15 has already begun and one of the features I have added is an option to disable the directory monitoring falling back to 3.13 behaviors.
I won't release it until the monitoring problems have been solved.

Sorry for the inconvenience.
Thanks for your feedback

Remi

Welcome to this forum Maarten,

As Siren uses high level functions to rename, copy etc. files I don't think this problem is linked to GPT.
My first ideas bring me to think to two possible root causes :
1) Maybe is it a privilege problem. Have you tried to execute Siren as Administrator ?
2) Maybe is it due to the fact that the partition you are working on is bigger than 2 TiB. I have never tested Siren in this configuration.

To investigate further can you tell us the operations you tried to achieve and the resulting error messages ?

Thanks for your feedback.

Regards

Remi

Hello,

I know there are some small and various display issues with different desktop environment and themes.
These problems are difficult to fix.
Thanks for reporting it.

Can you please tell :
- What is the distribution you are using ?
- What is the desktop environment ?
- Do you use any theme ?
- Did you make any modification to the theme you use ?

About the forum and the double quotes : I have made some tests and all looks fine.
I have changed the title of this topic by surrounding 3.14 with ".
Maybe didn't I understand what you meant.

Regards.

I join you to wish to everybody a happy new year 2014.

Stefan, once again, thanks a lot for your support.

Thanks !

Your command line looks incomplete/malformed. It should end with "-r -q", right ? (without the space between "-" and "r").
I wouldn't want the other users to be misinformed.

Welcome to this forum MrPete,

To investigate it would be easier to work on some of the files on which the different issues appear.
If needed you can send them to me by mail at the address you'll find in Siren's "?/About ..." window.

Thanks a lot for this bug report.