survey: Incremental search usefulness



  • @cmeriaux

    I’m tired trying to convince mr Ho.

    Thx for trying and spending the time creating the code, issue and PR.
    It’s a pity that it isn’t considered to be a useful enhancement.



  • @Alan-Kilborn said:

    Also, one presumes that dot matches newline would never be enabled for this?
    As an example of why this would be bad:
    Type .* into the incremental search box and you are instantly sitting with your caret at end of file, with no great way to get back to where you started so you can do a better incremental search.
    Maybe the answer is, don’t type .*, but…

    I tried this in Visual Studio 2019.
    I noticed that .* will only match data out to the end of the current line.
    Thus it doesn’t appear to have a . matches newline capability.
    Also, I couldn’t get any regex string to cause a “jump” of the viewport when a match starts on the current viewport but logically extends to higher document positions.
    My original concern stems from N++'s search behavior of wanting to put the caret end of a selection at the higher document position and then making sure the caret is shown to the user.
    Hopefully this is understandable.
    Anyway, I like the way VS19 works in this regard, and if it ever gets accepted for N++, I hope it would work similarly.
    Still not a huge fan myself of regexing this, but if it is the “will of the people” I’d go along. :-)



  • @Alan-Kilborn said:

    Thus it doesn’t appear to have a . matches newline capability.

    Hmmm, I may have to retract that. Or at least qualify it, because the way it works I don’t think one can tell exactly what it is matching. It could be matching each line individually, or have one match. I think the visual highlighting would be the same either way. (Again, I’m talking about VS2019 behavior, not N++).



  • A POSTING related to the current thread that somehow hasn’t been mentioned to this point.



  • @Alan-Kilborn

    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:

    1. Using “Highlight All” makes N++ scroll the viewer despite that valid match is already present on the screen:

      animation

    2. 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”:
      npp_regexp.png

    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.




Log in to reply