Hi,
Here is a bug about presets sometimes not saving in the replace window in regex mode.
I believe it has something to do with the name of the preset.
The bug is two-fold. I was tweaking a regex search-and-replace.
-
When it looked good, I hit "Save Preset". Then I clicked cancel from the Replace operation, as I didn't want to rename the files (I was just setting up the regex at that stage). When I went again to look at my carefully honed preset, the saved preset was not in the list!
-
The second time around, I re-created the regex pattern /pull you hair here/ , saved the Preset, and clicked OK to replace. The replace failed because one target rename collided with an already renamed file. I went to look at the preset: Not in the list again!
To clarify, this bug is about saving presets. (Not about target collisions, regex patterns etc.)
It is pretty annoying as bugs go as I wasted time tweaking the regex (twice more than needed).
Here is everything you need to duplicate the bug.
- Create two files named:
ab.1.2.txt
ab.1.2....txt
/*
The idea of the preset is to replace every dot in a file name with a space, except:
(i) the dot before the extension
(ii) trailing dots just before the extension, which are just nuked instead of being replaced by spaces.
/*
- Select the files, open the replace window in regex mode.
- For the pattern, paste ([^.]+).(.?)(?:.).([^.]+)$#
- For the replace, paste \1 \2.\3
- Save the preset, pasting this exact name: Replace Dots w Space try ab.1.2...txt
- Click OK.
The replace will fail because the second file with collide with the first.
Open your replace window: the preset is gone.
I tried with a simpler preset name (test preset) and did not have that problem.
In case you are wondering, the long preset name ("Replace Dots w Space try ab.1.2...txt") was there to remind me of the pattern's behavior (that's why it contains the name of a test file name.)
Wishing you all a beautiful weekend
