Hello @veridigital and All,

I think, indeed, that @veridigital asks a rather embarrassing question…

If we suppose that the problem of the NUL characters, following a power cut, comes from a setting, concerning the writing on the HDD, how to explain that it acts, specifically, on the files opened in Notepad++ ?

In theory, corruptions should occur, in a random way, on any file opened by any software !?

Seemingly, the NUL bytes story is not ended ;-)) It’s really irritating !

Best Regards,

guy038

P.S. :

Reading the @peterjones answer more carefully, I understand that Notepad++ is based on MS API. But it should certainly not be the only software ! Also, why should problems privilege Notepad++ files ?

Hello Ekopalyse,
That works fine!
Thank you very much.

@Ict-MylabDev said in Error with newlines from barcode scanner:

found that turning off “Enable auto-completion on each input” solved the problem.
I have no idea what this feature is doing exactly.

Specifically, what is happening: as you continue to scan CODE39 with the barcode scanner, it is typing C O D E 3 9 EOL. With autocompletion turned on, the first time through, Notepad++ auto-complete doesn’t do anything (nothing to autocomplete, because it’s never seen that before). The second time, after n characters from CODE39, the autocompletion mini-window appears (because it recognized the start of CODE39, which it has now previously seen), and it keeps matching as the scanner types the remainder of CODE39; the EOL at the end of the barcode scan, instead of inserting a newline in Notepad++, is used to select the active word from autocomplete, so it just leaves CODE39 but stays on the same line. The third barcode scan starts on that second line, but since it’s extended the text beyond CODE39 to CODE39C..., it isn’t matching, so the third EOL goes to Notepad++, to move the cursor to the third line. Similar sequences occur on future rows, which explains why it grows for a while. Apparently, it hits a maximum length for autocomplete on the 12th line, hence it just stays the same length, because it listens to that lase EOL on that line.

(This can be replicated on your own without a barcode scanner by just turning on the autocomplete, and typing (not just pasting) CODE39 followed by a newline many times.)

Hello, @gstavi,

Reading your post to @plazer1, I decided to give it a try ! So, I saved all events, detected by Procmon, regarding the Notepad++.exe process, in a log file, when Notepad++ starts-up !

Note that my N++ 7.8.3 configuration works fine !! So, it’s just a test and not a debugging task !. However, if you don’t mind, I would like to send you this small log file ( ~840 Kb ), with few comments of my own !

My e-mail address is

Again, I’m not requiring any help from you, but I just curious to know your feelings about it, as your knowledge of the Procmon utility is, of course, much better than mine.

Thanks by advance !

guy038

That did it. Both ways. For some reason since I could only find one Notepad++.exe in the folders, i did not think ti simply search my hard drive. This is a work computer and I am not very well versed in how Windows is administered for a group. My directories for the exe look like this: “C:\ProgramData\App-V\39053732-F6F5-4330-B230-69A64467D68E\53CFA7AE-489B-47AD-9FC2-46755FB8FDAA\Root\VFS\ProgramFilesX64\Notepad++\notepad++.exe”

I do not even see a “ProgramData” at first. Then I thought to view hidden system files and then there it was. Thanks for giving my brain a jump start.

-Rick

@Alan-Kilborn Thanks for identifying the issue on GitHub. I’ve posted a comment on the thread (would love to be more technical on that comment… but had to be just a regular complaint…)

Hello, @adam-bowsky, @michael-vincent, @supasillyass and All,

Personally, I would use the following regex S/R, which should work in all the discussed cases !

I simply assume that the N90- string, with this exact case, is preceded with, at least, one digit !

SEARCH (?-si)^\h*\d+N90-.*\R?

REPLACE Leave EMPTY

Of course, the Regular expression search mode is selected and the Wrap around option is ticked

Give a try !

I’ll give you some explanations when everything is right ;-))

Best Regards

guy038

@Alan-Kilborn Apologies… I am not experienced with this.

@Alan-Kilborn Thanks! This is exactly what I needed!

I fixed the issues, The dll needs to go as follows;

Notepad++ install directory\plugins\ComparePlugin

And now it works!

Got it ! thanks, WORKS !

@Sylvester-Bullitt Sounds like Notepad++ is not the tool for the job.

@PeterJones Thanks for the clarification!

Expanding a builtin language for anything other than a keyword is not something you can do without access to the source code.

You could use a User Defined Language, but you’d probably feel it didn’t meet all your needs. If that was enough, a UDL will allow \\ to mark a comment line, like so:
f71846ac-63a9-4a88-b670-384ca07fe399-image.png

However, you can add extra highlighting to a builtin lexer (like the SQL lexer) using regexes via the script EnhanceAnyBuiltinLexer.py that @Ekopalypse shares in this linked post

“Until EOL” is easy: DELIMITERn open = :, close = ((EOL))
Unfortunately, stop-on-other-whitespace is harder; not sure how it could be done natively in a Notepad++ UDL.

There are two alternatives that I can think of:

just define it as a delimiter with ((EOL)) closing it, but set the STYLE for that delimiter to allow nesting of anything else (that you have defined). For example, if = was defined in Operators 2 as magenta, Number defined with blue foreground and cyan background, Keywords 1 defined as Green/Bold with Area as the keyword, and DELIMITER1 defined with open = :, close = ((EOL)) and foreground=red, bg=yellow, nesting=operators2+numbers, I see:
7f97a779-14f3-4046-b719-3abb641fdf54-image.png
which might be enough for you. Otherwise, you can add extra highlighting to a UDL language using regexes via the script EnhanceUDLLexer.py that @Ekopalypse shares in this linked post

@Adnan-Haddad

install procmon, set a filter for shortcuts.xml and run it.
Start npp and see where it is loading the file from.
Make your changes and close npp.
Check if procmon informs about any error or whether npp
was able to save it correctly.