Find and Display *All* Duplicate Lines

Alan Kilborn

Another reason is that I have a UDL that I made for .sr files which colorizes the output somewhat like N++'s Search results,

Actually, I misspoke. When I first set it up, I was trying to do it with a UDL, but I later switched to using the EnhanceAnyLexer plugin. (I was confused because I didn’t delete my UDL when I went a different way)

EnhanceAnyLexer seems easier than trying to force N++ to artificially use the internal Search-result lexer, but it is definitely interesting to play around with something like that, so I enjoyed considering the code from @Michael-Vincent and @Ekopalypse earlier in this thread.

guy038

Hello, @yaron, @coises, @mkupper, @alan-kilborn and All,

From this post :

https://community.notepad-plus-plus.org/topic/20370/how-to-jump-to-a-bookmark-and-show-the-bookmarked-line-at-the-top-of-the-screen-not-in-the-middle/14

In order to always get the target line on top of the visible screen, @mkupper, simply add these 3 Python lines :

                        curr_pos = editor.getCurrentPos()
                        curr_line = editor.lineFromPosition(curr_pos)
                        editor.setFirstVisibleLine(curr_line)

right after the line

                        editor.gotoLine(line_in_source_file)

in the FindAndDisplayAllDuplicateLines (FADADL) Alan script

Just be sure that the parameter Enable scrolling beyond last line is checked, in the Preferences > Editing panel

Now, @mkupper and @alan-kilborn, to get rid of the random selection issue, I personally solve the problem by moving the DupeLineResults.sr file in the secondary view ! And , in that case, it does not bother anymore about a possible previous selection, in the DupeLineResults.sr file, right before double-clicking to get an other line ;-)

WOW…, Alan, everything is perfect with your script, by now !!

Best Regards,

guy038

Alan Kilborn

@guy038 said in Find and Display *All* Duplicate Lines:

In order to always get the target line on top of the visible screen, @mkupper, simply add these 3 Python lines :

                    curr_pos = editor.getCurrentPos()
                    curr_line = editor.lineFromPosition(curr_pos)
                    editor.setFirstVisibleLine(curr_line)

right after the line

                    editor.gotoLine(line_in_source_file)

You shouldn’t have to calculate new values (your curr_pos and curr_line).

editor.setFirstVisibleLine(line_in_source_file) should suffice.

to get rid of the random selection issue, I personally solve the problem by moving the DupeLineResults.sr file in the secondary view ! And , in that case, it does not bother anymore about a possible previous selection, in the DupeLineResults.sr file, right before double-clicking to get an other line

I can’t comment, as I can’t reproduce random selections happening.

Alan, everything is perfect with your script, by now

Well, I doubt this, given mkupper’s continuing strange issues with it.

EDIT: Ah…wait… I may have just had an inspiration on what could be happening for mkupper, even though I can’t repro it. I’ll do some more thinking on it, and if its logic is sound, I’ll post about it…

guy038

Hi, @yaron, @coises, @mkupper, @alan-kilborn and All,

So, as @alan-kilborn mentioned, to always get the target line on top of the visible screen, @mkupper, simply add this line :

                    editor.setFirstVisibleLine(line_in_source_file)

Right after the line

                        editor.gotoLine(line_in_source_file)

But I forgot to specify that your must cancel, as well, the Word wrap feature. That is IMPORTANT !!

BR

guy038

guy038

Hi, @alan-kilborn and All,

An other minor bug :

If you do get a DupeLineresults.sr file in a tab and that the corresponding source file is presently closed, any double-click on a line of the DupeLineResults.sr file will not open the source file, contrary to a double-click in the Search results panel !

BR

guy038

Alan Kilborn

@guy038 said in Find and Display *All* Duplicate Lines:

If you do get a DupeLineresults.sr file in a tab and that the corresponding source file is presently closed, any double-click on a line of the DupeLineResults.sr file will not open the source file, contrary to a double-click in the Search results panel !

Yes, well a compromise here, because this is only a single source file situation – not multi-file like a potential find-in-files – is that you already have the source file open in another tab. :-)

We can fix it with…more code… The original intent, like most of my scripts, is just a demo of possible functionality, not all-encompassing behavior. To try to do that…scripts get too long and the main point is lost, with all the error-checking needed, and the full-featuredness ratcheting up the line count…

Alan Kilborn

@guy038 said in Find and Display *All* Duplicate Lines:

But I forgot to specify that your must cancel, as well, the Word wrap feature. That is IMPORTANT !!

Do we call this YOUR bug, since you introduced the “setFirstVisibleLine” code? :-)

I didn’t try it, but probably changing:

editor.setFirstVisibleLine(line_in_source_file)

to

editor.setFirstVisibleLine(editor.visibleFromDocLine(line_in_source_file))

will cure that.

mkupper

Thank you @guy038 on the editor.setFirstVisibleLine(line_in_source_file) thing. That works perfectly and now I’m consistently taken a view with the desired line at the top.

@Alan-Kilborn, as the results are now more consistent I spotted a clue related to the random selection. The end of the random selection is at or very near the mouse which is there because I was double clicking on the line in the DupeLineResults.sr file. The typing cursor is also at that spot.

When we double click on a word in npp that word becomes selected. When working with DupeLineResults.sr I double click on a line and am usually double clicking on the number part of Line 1234 though I could double click on the word Line. I’m now wondering if npp or Scintilla is still in the middle of painting that double-clicked word in the DupeLineResults.sr tab while the FindAndDisplayAllDuplicateLines.py script is running notepad.activateIndex(view, index)

I tried an experiment with starting a bunch of CPU bound processes to tie up the machine but was unable to hit the sweet spot of getting random selections to happen every time. I did discover that if I use start /high when starting a CPU bound thread that having all of my CPU cores running high priority threads results badly performing windows. I killed one of those threads to free up a CPU core and both Windows and Notepad++ work very well.

datatraveller1

Hi @guy038 a bit off topic but…
Congratulations on being the top 3 poster now!!!
Thanks for your great contributions to the Notepad++ community.

Alan Kilborn

If you’ve used a script in this thread, you might want to double check your copy of it for a bug I’ve discovered.
Look to previous postings in this topic thread where the script has been changed – find the text moderator edit (2024-Jan-14).
There’s a link there that describes the bug in more detail, and shows what needs to be changed in an old copy (or you can simply grab a copy of the current version).