Highlighting with self created words in "langs.xml" does not work
-
Classic repeating without thinking from my side 😂
-
Your understanding of how the current version of EnhanceAnyLexer works is correct :-)
If you need help getting started with V, let me know. There are some hurdles that are not so obvious. Either message me or open an issue on github.
As for substyles for existing lexers, hmm … without having given it much thought, I assume it can be added. Basically we just need some additional styles and their configuration and apply them when activating the buffer.
Should be doable. -
I said earlier,
No one has put in a feature request with Notepad++ to implement these substyles. Until someone does, it’s guaranteed to never be implemented in core Notepad++.
I actually just put in the feature request for the main app.
The more I thought about it, the more I thought it would work best in the main app, where the keyword list and color definitions could all go in the Style Configurator, alongside the normal keyword lists. I think I’ve figured out the places I’d need to edit, and I’ve offered to do the work and put in the PR, if Don gives his stamp of approval on the general concept.
If he rejects the concept, I’ll start exploring other options.
-
Tried now the PythonScript solution. Could not really reliable get it working.
First, it did not colorize on startup of NPP. Accidentally, I found out, that it starts colorizing if I open the PythonScript console. Output by the way is below. Solution after some looking around was to change the initialization type from “LAZY” (default after installation) to “ATSTARTUP”.
Second, trying with an arbitrary PHP keyword (here CURLOPT_STDERR) does not work. No clue why.
This is the relevant part of
SubStylesForLexer.py:self._style[SCE_HPHP_WORD].append(dict(fg=(0,135,68), bg=(255,255,255), keywords="pryrt_a")) self._style[SCE_HPHP_WORD].append(dict(fg=(0,0,255), bg=(255,255,0), keywords="pryrt_b")) self._style[SCE_HPHP_WORD].append(dict(fg=(0,135,68), bg=(255,255,255), keywords="CURLOPT_STDERR"))This is my test PHP script (results see comments):
<?php pryrt_a "xyzzy"; # works as expected :-) pryrt_b "xyzzy"; # works as expected :-) $test = CURLOPT_STDERR; # does not colorize :-\ ?>What am I doing wrong?
However, if the feature would be implemented nativ in NPP, that would be much better :-)
Placed my 👍 already at GitHub :-)–
Just for information, the PythonScript console output:Initialized SubstyleLexerInterface Python 2.7.18 (v2.7.18:8d21aa21f2, Apr 20 2020, 13:25:05) [MSC v.1500 64 bit (AMD64)] Initialisation took 15ms Ready. -
First, it did not colorize on startup of NPP. Accidentally, I found out, that it starts colorizing if I open the PythonScript console. Output by the way is below. Solution after some looking around was to change the initialization type from “LAZY” (default after installation) to “ATSTARTUP”.
That was explained in the FAQ: How to install and run a script in PythonScript I linked you to originally, in the instructions for how to get it to run automatically. I am sorry you didn’t notice that.
Second, trying with an arbitrary PHP keyword (here CURLOPT_STDERR) does not work. No clue why.
This is the relevant part of
SubStylesForLexer.py:self._style[SCE_HPHP_WORD].append(dict(fg=(0,135,68), bg=(255,255,255), keywords="pryrt_a")) self._style[SCE_HPHP_WORD].append(dict(fg=(0,0,255), bg=(255,255,0), keywords="pryrt_b")) self._style[SCE_HPHP_WORD].append(dict(fg=(0,135,68), bg=(255,255,255), keywords="CURLOPT_STDERR"))What am I doing wrong?
Apparently, the lexer used for PHP requires all the keywords to be in lowercase. To make it work, just change the case of your keyword to lowercase. (This makes it match the case it was before you removed
curlopt_stderrfrom the list instylers.xml, too):self._style[SCE_HPHP_WORD].append(dict(fg=(0,135,68), bg=(255,255,255), keywords="curlopt_stderr"))
But as a second note: I noticed that you did two different
.append()calls for the same color. Each.append()creates a new list. The intention, if you have multiple words you want the same color, is to have multiple words in the string for the same.append(), like:self._style[SCE_HPHP_WORD].append(dict(fg=(0,135,68), bg=(255,255,255), keywords="pryrt_a curlopt_stderr more words go here")) self._style[SCE_HPHP_WORD].append(dict(fg=(0,0,255), bg=(255,255,0), keywords="pryrt_b and other secondcolor wordish thingies"))Here’s a screenshot showing various words from those multi-word lists highlighted, proving it only needs
However, if the feature would be implemented nativ in NPP, that would be much better :-)
That will take a while, since I’ll just be working on it in my free time. Like you, I am not paid to develop the Notepad++ application. In fact, until this year, I had never contributed any actual code to the codebase (though I had done a couple of XML config default updates over the years, and I am heavily involved in the Notepad++ documentation). But as a code-contributor, I’m a newbie to this project, and the Notepad++ codebase is a large, complicated critter to navigate.
Depending on how long it takes me, it might not even be done in before the next release. But I will work on it as I have time, and I will report back here when/if the PR gets merged – after that happens, it will be the version after that announcement that it makes it into the Notepad++ application.
Apparently, I’ll have to pay attention to which lexers require the keyword lists to be in lowercase, and either document that well, or have my code fix the case for those lexers. So thanks for that heads-up.
-
if the feature would be implemented native in NPP, that would be much better
Actually, the end result would be the same.
You’re probably just saying that because the script setup takes you outside your comfort zone.
You’re lucky that the author of Notepad++ has agreed to accept changes to have it be native; this often does not happen, and add-on scripts to add features or change functionality are all one has. -
@PeterJones
Can confirm now, that for me the PythonScript solution fully works. I added 1963 constant and 103 language construct keywords and special vars to SubStylesForLexer. py with different colors and all lowercase. The 1270 function keywords still are in the NPP definitions (langs.xml and stylers.xml). >Thanks a lot for your great job!<So I will uninstall the EAL plugin now and stay with substyles.
@Alan-Kilborn
No, I do not have a “need native solution” comfort zone. My only argument to have a NPP solution was performance. Nothing else. I never had and have a problem with script setups or similar. -
@Manfred-Drechsel said in Highlighting with self created words in "langs.xml" does not work:
for me the PythonScript solution fully works.
Glad to hear it. (For future readers of this discussion, I have updated the downloadable script to make the ATSTARTUP more obvious (it’s now in the comments near the top of the script, not just in the instructions-FAQ)
My only argument to have a NPP solution was performance. I never had and have a problem with script setups or similar
If you haven’t had performance problems with other scripts, you likely won’t with this one, either.
The only time the script comes into play is when you change from one document to another (the
on_bufferactivated) – and that’s a brief number of commands that shouldn’t take a noticeable amount of time. (There might technically be a difference, but with how few commands it is, it would be on the order of a tiny fraction of a second of difference.)Once the
on_bufferactivatedhas been run, Scintilla will do the actual lexing and syntax highlighting using the code compiled into Notepad++, whether theon_bufferactivatedstuff was run from a script or from native Notepad++, so the syntax highlighting will not have any performance difference. -
@PeterJones said in Highlighting with self created words in "langs.xml" does not work:
If you haven’t had performance problems with other scripts, you likely won’t with this one, either.
My comment was wrong and misleading. For whatever reason, I had the regex way of EnhanceAnyLexer in my mind. Using substyles is native, as you already explained earlier. Sorry for the confusion…
-
I’m sure you already know that this is possible:
I added the option to set my PHP constant words to bold:
editor.styleSetBold(subStyle, self._style[parentStyle][idx]['bold'])self._style[SCE_HPHP_WORD].append(dict(fg=(0,0,204), bg=(255,255,255), bold=True, keywords="..."))More options available here or here (search for STYLESETBOLD or STYLESETITALIC or STYLESETUNDERLINE …)
-
FYI: The developer accepted my PR, which means it will be native Notepad++ (showing up in Style Configurator) at the next release.
-
Yes, I followed the other discussions. Great job!
-
which means it will be native Notepad++ (showing up in Style Configurator) at the next release
It can be seen in v8.7 RC Announcement item 13.
The PHP keyword list has also been split from the original single huge list into a couple of huge lists instead.
My recommendation, if you are trying out v8.7 (whether it’s the release candidate, orthe final v8.7 in a few weeks, or if you are reading this later and updating from something before v8.7 to anything at or after v8.7) and want to be able to see the new styles in Style Configurator:
- If you just download the Portable version of v8.7, you can try it out without affecting your installed copy, and you will be
- If you install v8.7 overtop an older copy (upgrade or otherwise just run the installer), it will not update your
stylers.xml, other themes, andlangs.xml, so you will not see the new styles in the style configurator right away. Instead, follow one of the following sequences:- If you don’t have the PythonScript plugin and don’t want to use it, then you can manually compare the new
<installed directory>\stylers.model.xmlto your%AppData%\Notepad++\stylers.xmlor theme file, and bring in the new stuff from the .model. into your active file, and restart. (This is mentioned in the User Manual here.) - If you have the PythonScript plugin, or are willing to install it, then I highly recommend following the instructions in “Config Files Need Updating, Too” (I suggest with PythonScript 3, but it will work with the PluginsAdmin-version of PythonScript 2 also)
- If you don’t have the PythonScript plugin and don’t want to use it, then you can manually compare the new
—
For those who are frequent users of PythonScript, I recommend the following customization after running my script on v8.7: open
stylers.xml(or your active theme’s XML), go to the “Python” section, and replace the rows for “User Keywords 1-5” (styleID 128-132,substyle1-5) with something similar to what’s in this gist. (Sorry, it’s too big to fit in a post in the forum: there are a lot of keywords)After restarting Notepad++, then the Style Configurator will call the “user keyword 1-5” styles as “PythonScript xxxx”, and the user-defined list will be pre-populated with PythonScript’s built-in objects,
editor-object methods,notepad-object methods, enum classes and enum elements. You might not like my choice of colors (I am not a graphic designer, after all), but it’s split up in such a way that you could make them all the same color if you want (if you don’t want to mentally distinguish those categories), or you could make the colors wildly different, if my subtle differences in color from the standard Python KEYWORD style isn’t distinct enough for you.original v8.7 Python styling: 
with PythonScript keyword lists: 
-
Just installed a clean version of NPP V8.7 after i read your comments here ;-)
Tomorrow, I will insert all the keywords from my PHP V8.4.0beta5 into the style definitions and restore my colors.Only a minor issue which I’ve seen is the width of the style selection list control. It should be wider to see the full text of the styles. See attachment. Guess I directly should file an issue for NPP?
The NPP SubStyle functionality looks really great now and again, many thanks and I appreciate your efforts very much :-)
-
@Manfred-Drechsel said in Highlighting with self created words in "langs.xml" does not work:
Only a minor issue which I’ve seen is the width of the style selection list control. It should be wider to see the full text of the styles. See attachment. Guess I directly should file an issue for NPP?
It’s always been that way (see for example, the “INSTRUCTION WORD” on ActionScript, or the “Indent guideline style” in Global Styles, both of which have gone beyond the width for multiple versions of N++).
If you want that aspect of the GUI changed, you would need to put in a feature request in N++'s GitHub repo. I would suggest asking for either resizable, or wider-by-default, or at least having a hover (or having a hover plus resizable/wider).
I am highly doubtful that the Developer would implement be wider-by-default; there’s slightly more chance that he’d make it user-resizable; I would say the best-chance for implementation is using the full Style name as the hover text for each entry, which is why I suggested it, but no guarantees it would be implemented.
