@Hans-van-Gelderen ,

I am using the “Bespin” theme.
The theme, which is just a color/style mapping of identified keywords in a certain context, should be irrelevant.

If the theme were set up correctly, then it would be irrelevant. But maybe the theme is out of date.

Think of the theme as a mapping from the named settings in Notepad++ to the numbered array in the lexer (which is part of another separately-maintained codebase, known as Scintilla).
Assume, for example, that in the “old days”, the CSS lexer expected “SETTING A” to be mapped to ID=1 and “SETTING B” to be mapped to ID=2. Then assume the “Bespin” theme was created. Then assume Scintilla changed the CSS mapping to expect “SETTING A” to be mapped to ID=3 and “SETTING B” to be mapped to ID=4. The default theme in Notepad++ was then updated, but no one updated the “Bespin” theme. So you tell the Bespin theme “I want these colors for SETTING A and SETTING B”, and the theme maps those to ID 1 and 2, and the lexer doesn’t see them because it’s looking for 3 and 4. Hence, the theme is not irrelevant to the conversation. (Note, I am not saying this is for-certain the case for the Bespin theme and CSS lexer; I am just saying it’s not out of the realm of possibility; I use the default theme, and rarely edit standalone CSS.)

Thus, because it might very well be the theme, for debugging purposes, please try the default theme.

If you are in the position to get Notepad++ enhanced in this respect

This is a forum for the Community of Notepad++ users. Some here have contributed to the codebase, but the primary developer uses the forum mostly for announcements. And this is especially not a 1-on-1 support desk, where you can expect that I am now committed to solve your problem for you – I voluntarily read and answer in this forum, to help other Notepad++ make good use of the tool, but I am not part of the “in crowd” or a paid employee, and you cannot assume that I will always be available.

Feature requests and bug reports do not go in the Forum – but really, the forum is a good first-line of support, to help educate users before feature requests are made: maybe there is already a way to accomplish the goal in an alternate manner.

I noticed also other keywords in HTML, CSS and Javascript colored/styled wrongly

If it’s colored or styled wrongly in the default styler, then show us where you think it’s wrong, and there’s probably a bug (or a misunderstanding of what the correct behavior is); otherwise, the theme is likely to blame. As I’ve said, the developers don’t regularly update the themes that are bundled with Notepad++.

…and here is the link to the GitHub feature request:

https://github.com/notepad-plus-plus/notepad-plus-plus/issues/8153

@abdulbadii

OR…you can just create your own forum for discussion of your fork, and don’t muddy the waters here!
Thanks.
:-)

Ok, I figured it out…
Turns out that the langs.xml file in my profile folder was seriously outdated. Many languages (among them Java) were missing, and once I’ve updated it with a new version I am now getting proper highlighting of Java.

@dinkumoil said in Uh oh, virus commentary pending?:

see my comment at the issue tracker entry.

Yes, it’s why I titled this thread with “Uh oh” :-)

This PS, saved as startup.py (user NOT machine and PS configuration changed from LAZY to ATSTARTUP) should do the trick

e6fb0b18-db39-4bab-a14c-ebdea5b99411-image.png

from Npp import notepad, MENUCOMMAND if '-tailmode' in notepad.getCommandLine(): notepad.menuCommand(MENUCOMMAND.VIEW_MONITORING)

and npp like this notepad++.exe -multiInst -nosession "FULL_PATH_OF_THE_FILE" -z -tailmode

Hi, @craksoft, and All,

You said :

So this long thing (?-s)(?<=\d{4}-\d\d-\d\d)\h+.{8} is 6 number ?

I don’t know what you means, exactly !?

The regex expression (?-s)(?<=\d{4}-\d\d-\d\d)\h+.{8} deletes blanks characters and the next 8 characters, when preceded by a date, with the YYYY-MM-DD format. No more, no less :-)

BR

guy038

@Jack-Adrian-Zappa said in Notepad++ losing unsaved documents:

but that means that some update turned it off,

Maybe “some update” was pretty smart, protecting you from features currently in question. :-)

I would think that should be a priority to fix.

There’s been some attempts.

@Hadi-Jam

if you want it to be always on top then start npp with the command line paramter -alwaysOnTop.

@Michael-Vincent said in Need the ability to have fixed-width line number column:

(Scintilla multiedge)

You mentioned “multiedge” briefly above; I agree that this could definitely help the OP. And, it appears a native multiedge capability is coming soon to Notepad++ !

See https://github.com/notepad-plus-plus/notepad-plus-plus/pull/8107 and :

f8d30148-91ff-48c1-a887-3c9de23250d5-image.png

Hi @guy038

Thank you, your’s is good advise, as well as @Alan-Kilborn’s. As I told him, I only took into consideration the Windows case, ignoring other platforms.

Will try to not forget it.

Best Regards

@chilkoot

Great! It is good to hear that it worked for you.

Best Regards.

The discussion is continued HERE.

The discussion is continued HERE.

@khk-khk

I’m not sure why you are opening a separate new thread each time you are replying, but OK, it is good that things are making sense on your end! :-)

@dail

Yes, that makes sense. As I said in my earlier post, the picture looks fine… but not nice.

Hello, Hi, @tư-mã-tần-quảng and All,

I forgot to explain my regex S/R :

SEARCH (?s-i)(\h+<name>.+?)(\h+<id>.+?\R)

REPLACE \2\1

So :

First, the part (?s-i) has already been explained by @alan-kilborn !

Then, the part \h+<name> searches for some horizontal blank characters, followed with the string <name>, with this exact case

Now, the part .+?, due to the s modifier, looks for the shortest non-null range of any char, even EOL ones, till … some blank chars, again, followed with the string <id>, with this exact case

The two parts above are stored as group 1 because of the surrounding parentheses. Note that it, necessarily, ends with EOL chars, as followed with the <id> line !

Then the part \h+<id> matches any horizontal blank chars, followed with the string <id>, with this exact case

Finally, the part .+?\R matches the shortest non-null range of any char till… the next EOL chars, so ending the <id> line

Again, the two parts above are stored as group 2 because of the surrounding parentheses.

Note that the \R syntax stands for any kind of line-break ( \r\n for Windows files, \n for Unix files and \r for Mac files )

In replacement, the \2\1 rewrites, in reverse order, the single-line group 2 ( line <id> ) and the multi-lines group 1

Best Regards,

guy038

@khk-khk Thanx to all - I’ll try

@Alan-Kilborn said in How to opt out of OAuth App but continue to have access to the NPP forum?:

Just a bit more, here…

Thanks for the clarification: that was probably wise to add the extra information.

@guy038

in case of overlapping matches

Well, I meant non-overlapping matches of course. Often while marking data it is simpler to come up with 3 or 4 successive marking operations on different data in order to capture everything you want; coming up with one regex, while perhaps an interesting exercise, would likely be distracting from your at-hand task.