survey: Incremental search usefulness
-
I seem to have missed those messages, I’m answering right now. Sorry about that.
-
I have created feature request at GitHub — https://github.com/notepad-plus-plus/notepad-plus-plus/issues/8278
@cmeriaux , I have experienced a few bugs, not sure if these are unique to my configuration yet:
-
Using “Highlight All” makes N++ scroll the viewer despite that valid match is already present on the screen:
-
Not all matches are highlighted. Testing on the following snippet:
{ "guid": "{xx-xx-xx-xx}", "name": "Command Prompt", "commandline": "cmd.exe", "icon": "ms-appx:///ProfileIcons/{xx-xx-xx-xx}.png", // "colorScheme": "Campbell", "antialiasingMode": "cleartype", "closeOnExit": "graceful", "cursorShape": "bar", "fontFace": "Consolas", "fontSize": 10, "hidden": false, "historySize": 9001, "padding": "8, 8, 8, 8", "snapOnInput": true, "startingDirectory": "%USERPROFILE%", "useAcrylic": false }
Only the first one is highlighted and only two matches are highlighted after pressing “Enter”:
Will continue using this build and report back if more bugs are found.
-
-
@asvc Thanks for the futur request.
The regexp issue may be related to the one already opened on github tracker -
@cmeriaux said in survey: Incremental search usefulness:
The regexp issue may be related to the one already opened on github tracker
Which one? I might have missed the link.
-
@cmeriaux said in survey: Incremental search usefulness:
here is a survey about the “incremental search” usefulness.
Do you use it ?
Yes.Do you need regular expression support ?
In general, yes of course. I would not even consider using a text editor w/o regex support. However, specifically in incremental search, no.Do you need an incremental mode in the find panel ?
Do you need an incremental mode in the replace panel ?
Do you need an incremental mode in the mark panel ?
No. -
-
Not to beat a dead horse, but this is related to incremental search.
When I use incremental search and tick both “Highlight all” and “Match case”, do my search then close Notepad++. Upon re-open, they are not ticked anymore. Seems incremental search options are not saved in config.xml the way regular Find panel options are.
I think that would be nice improvement to incremental search that wouldn’t ruffle too many feathers?
Cheers.
-
If you’re saying that to @cmeriaux , well, then I think he already had that idea: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/7753
:-)
But…it appeared from that that at least part of the problem was fixed already??Someone else had a somewhat-related idea in just the last 24 hours: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/8375
Both are good ideas, I think.
-
I was saying it to anyone that would listen - I can always count on you :-)
I think my question / idea is a bit different. @cmeriaux 7753 does appear fixed, opening the bar, selecting options, closing bar, reopening bar - my selections are still there. I proposing to close the Notepad++ application altogether.
Then re-launch Notepad++ application (maybe this is where 8375 fits in - remember the “show” status of incremental search) - either way, my selected options are forgotten.
Contrast that to opening the Find dialogue between Notepad++ application relaunches, things like “Match whole word”, “Match case”, “Search mode” - they are all remembered - saved in config.xml.
I was wondering if the two check options in Incremental Search (and maybe the visible status of the bar itself) can be GUI options saved in config.xml?
I guess a feature request if I really want it.
Cheers.
-
@Michael-Vincent I thinks add incremental parameters to the global config file is a good idea.
I’ve already proposed this feature on the conversation of this feature https://github.com/notepad-plus-plus/notepad-plus-plus/pull/8248#issuecomment-626377716 but author reacted with a thumb down. So I doubt it would be accepted.
But you can write a new issue on github, the author may change it’s opinion… we never knows -
Has there been any traction on incremental search with regexp support?
I went through the NPP’s GitHub page and the Issue #8248 was last updated a month ago.
That being said, it reads like @sasumner is now slightly less critical of the idea :)
-
@asvc said in survey: Incremental search usefulness:
Has there been any traction on incremental search with regexp support?
Not that I’m aware.
-
@asvc I’m affraid that the war has been lost, the feature won’t be implemented.
I’m sorry -
That feeling when you want to use a text editor, but it actively refuses to be used… I will try to poke @sasumner at GitHub one last time.
-
When one door closes, another opens. Let’s try with the fork: https://github.com/dail8859/NotepadNext/issues/4
-
@asvc said in survey: Incremental search usefulness:
the fork
Why do you think NotepadNext is a fork of Notepad++?
-
Hello, @don-ho, @cmeriaux, @alan-kilborn, @asvc, @ekopalypse, @michael-vincent, @astrosofista, @mapje71, @terry-r and All,
In order to promote a bit the incremental search, with regular expressions I just had an idea :
Why don’t we propose to put a new setting in the
config.xml
file to allow this new incremental search mode ? So, by default, for non-experienced users, the incremental search would remain a classical search ;-))I mean, in the same way that @don-ho, preserved the backward regex search with this new
regexBackward4PowerUser
attribute in theFindHistory
tag, since N++7.8.7 Release 4
. See my request to @don-ho, one month ago, for such a setting, in the last part of this post :https://community.notepad-plus-plus.org/post/54520
Just hope you won’t find this idea too ridiculous !
Best Regards
guy038
-
Nice fork. Qt is nicer than mfc. Too bad there isn’t a python API for plug-in because I don’t like Lua.
-
@guy038 your idea is a good compromise but I think for a feature like this, it should be mainstream wheter be hidden through a config parameter
-
@Alan-Kilborn said in survey: Incremental search usefulness:
Why do you think NotepadNext is a fork of Notepad++?
@cmeriaux said in survey: Incremental search usefulness:
@guy038 your idea is a good compromise but I think for a feature like this, it should be mainstream wheter be hidden through a config parameter
That’s a start! It can be used to gently introduce the functionality without creating any sort of discomfort for long-term users. Then, based on feedback, setting can be exposed in GUI.
Now… How to deliver this message to @donho without annoying him with repetitive requests? :)