Stumbling onto this feature request, I'd also like to say that this would be great to have. I'm fixing some legacy code right now and there is just A LOT of markers, but these "change visibility... to default" are simply unwanted and make it hard for me to see the correct markers by UCDetector.
Bump because this issue still exists and standard notepad is really really terrible for editing certain file formats. I know winrar is somehow doing this, because it just uses whatever system editor you have in place.
Bump because this issue still exists and standard notepad is really really terrible for editing certain file formats.
First of all: Thanks for spending so much time on this! In the meantime, I suspect using $(command) can get you unbroken highlighting. Thanks, ill use that.
Yeah, thats what i meant. It is actually braking the highlighting engine as a whole from what i can see. No line after it has any color; i expected the grey coloring (which Notepad++ uses) to end at the next quotation marks, but nope.
It works just fine, i just tested it on my ubuntu (the script itself usually runs on debian). This is the original line: https://pastebin.com/t2St7ePF Hilariously enough i cannot post it with the 3-tilde-code markdown, it breaks that. So basically A? ;)
Ah sorry, the ticks were swallowed by formatting. Here is a pastebin of it: https://pastebin.com/ZDD9NkxJ Anything after this line will be purple. (Don't forget to switch the language to shell)
Nested quotation mark not recognized properly (shell script)