Shouldn't share find input history with match input for Replace #5863
Replies: 7 comments 2 replies
-
|
by the way, it's an interesting idea, if you use a replacement, to store this pair of values somewhere in the settings for searching and replacing, for their subsequent quick use |
Beta Was this translation helpful? Give feedback.
-
|
I am puzzled by complex english text. pls reformulate: which input-history must differ from which? did I get it ok? -> history for find field in FIND MODE (when replace-field is hidden) must differ from history for find field in REPLACE MODE? |
Beta Was this translation helpful? Give feedback.
-
|
Yes. Find field in replace mode should only store in history when user calls replace or replace all. |
Beta Was this translation helpful? Give feedback.
-
|
must it depend only on mode of dialog (find/replace)? ie
|
Beta Was this translation helpful? Give feedback.
-
|
'replace with' field must use 3rd history list , of coz. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, something like this. Actually, for me it would be even better if replace with regex is also separated from non-regex replace, but I understand someone can think this would be confusing for the user. |
Beta Was this translation helpful? Give feedback.
-
I will keep this topic opened for n months. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
yes, it is the way how to add it. but this way is hard. many places of code refer to the field |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm almost sure this will be rejected, but I'll leave this here anyway.
Sometimes I need to do a mass replace using regex. Writing regex is not that trivial depending on the case, requires a bit of thinking, and the most complex part is obviously in the match pattern, not in the replace pattern which is more simpler like
$1lalala$2. I think I'll only need to run replace once, so I don't care about saving the pattern.Then, later, I realize I need it again, or at least something similar. The easy part is still there, in the replace input, I see the
$1lalala$2or if it's something different I can press up arrow key to access replace history.But what really matters, which is the text field just above, related to match pattern, was lost because I used find dozens of times since the last replace.
That's why I suggest to not share find input history with replace's match input. I understand it's expected that when user opens replace dialog the match input should be filled with last find input, this should continue as it is. But that value shouldn't be stored in "match history". While replace UI is open (with two inputs, one for match and other for replace), pressing up/down to navigate input history should only access values that once ran "replace" or "replace all" commands.
Beta Was this translation helpful? Give feedback.
All reactions