Search & Replace Strings - dropdown MRU ??

[bdeshi]

#123 is hardly scripted.

[PeterH]

#123 is hardly scripted.

Sure it's scripted - that *is* a script.

You only could argue about the used "scripting environment" - it's not a "standard script", or however you want to say.

[Papoulka]

v7.90.0078 - 2009-01-27 21:16
* MRUs: Now, patterns from the following commands are not added to
the command's MRU list anymore when triggered via scripting:
VisualFilter (::filter)
BatchRename (::rename "b")
RegExpRename (::rename "r")
SearchReplace (::rename "s")
KeepParticularChars (::rename "k")

Both scripting and the MRU are terrific features, and I'm sorry to give up either one, especially for S&R and RegExpRename. I'm sure there's at least a historical reason why they do not play nice together; but [REQUEST] maybe this can be revisited.

[bdeshi]

#123 is hardly scripted.

Sure it's scripted - that *is* a script.

You only could argue about the used "scripting environment" - it's not a "standard script", or however you want to say.

Well, my point was that ::rename is a scripting command that happens to call a function that is also used in GUI.
But the #command just triggers any arbitrary app menu, it's like hardwired kb shortcuts. Blocking MRU from #123 to me seems equivalent to blocking a part of a command just because it was called by a kb shortcut. again, it's because I see #commands similar to a kind of hotkey.

[TheQwerty]

History: http://www.xyplorer.com/xyfc/viewtopic. ... 556#p30556

We didn't catch that this applied to the CIDs as well as the keyword scripts back then but it does go against the spirit of the "wish":

The MRU list should be reserved for patterns explicitly typed by the user.

[admin]

To change it would mean to make an exception of an exception. Does not feel alright. Needs more meditation...

... ok, found a way.

[Papoulka]

... ok, found a way.

Thank you! This is really useful, especially for RegExp Rename where the strings are complex. Much appreciated.