Never mind. I figured it out. XML tells you where in Style Configurator to find settings.

The difference is probably because 'b and 'd will have normal digits (0-1 or 0-9) both before and after the 'b or 'd, whereas 'h will also have letters after. And since UDL defines it as a suffix, not an infix, it gets confused once there’s a non-numeric after the suffix. You might try to define all the hex prefixes you generally use in your Verilog in the Prefix 2 entry:

However, if you happened to have an 11-bit segment you tried to access as 11’h75A, but hadn’t included 11'h in your prefix 2, it wouldn’t highlight for you.

Is there a reason you aren’t using the built-in Verilog lexer? It defaults to Verilog for extensions v, sv, vh, and svh; I added vams (using Settings > Style Configurator > Verilog > User Ext).

I’m not a huge user of Verilog and its variants, but in the times I have been editing such files, I haven’t noticed any significant deficiency. It properly highlights any bitness for hex, binary, and decimal that I’ve noticed, and the other syntax I’ve used has looked reasonable.

If there are words that aren’t getting marked up using the Verilog lexer, you can use the Style Configurator to add custom words: both INSTRUCTION WORD and KEYWORD have a User-defined box for extending what gets highlighted.

Thanks @Claudia-Frank for explaining. Macro is working fine now…
And thanks @dail . yes. that is the one.

Appreciated

@Helloiam-Thomas

The easiest way, without regex:

Select the bloc you wanna replace and press Ctrl+H. Npp fills the Find what box automatically, with the proper codes inserted (although invisible, unless you try Find in files first; the results panel will show the Find string with the \r\n codes inserted properly).

Select the text to Replace with. Unfortunately, Notepad++ does NOT fill the box with the proper codes automatically. You need insert the \r\n codes at the end of each line manually.

some text**\r\n**
some other text**\r\n**
Comments**\r\n**
Comments**\r\n**
\r\n
(Value 1<)\r\n

Go to the end of each line and press Delete (it deletes the EOL codes, LF or CRLF).

some text**\r\nsome other text\r\nComments\r\nComments\r\n****\r\n***(Value 1<)*\r\n

Voilà!

@hh-hh

Fonts are part of the operating system, so try to find one which fits your needs and install it.
Afterwards use Settings->Style Configurator or define an UDL and choose the font you installed.
Never tried it myself, but I assume it should work.

Cheers
Claudia

@fuhrmanator

may I ask for what you need to define the blank lines?
If I understand this correctly, it is only used to let the GIFT engine know when
an new question starts.
Even if it could be done, it doesn’t get visualized.

What am I missing?

Cheers
Claudia

@Jackson-Bruch

for the sample data provided you could use a regular expression to search and replace
Find what:

and
Replace with:

This matches everything starting with G1 and ending with
G92 E0 ; reset extrusion distance followed by an eol char (make sure
you last line posted has this as well)

5x $0 means 5 copies from what has matched.

Cheers
Claudia

thanks, the one thing I didn’t try. works great. jon

@Nicole-Sigaud

if you edit shorcuts.xml you need to restart npp to make it happen.
In regards to the different action types you might want to take a look
here.

Cheers
Claudia

Thanks for confirming.

@shravan2x
Under the Language menu, look under “N” for “Normal Text”.

I’d also add that the NodeBB site has a lot of reports about broken searches, but since we don’t know what search plugin this site uses, it’s hard to tell what’s going on. But I would agree with Jim, the site search is very broken. Searching “langs” in the title only, you get things like “links” or “long”. I’ll take a page from Claudia’s book and use a search engine, but that won’t help with random people coming here to search for issues and then promptly giving up and putting in duplicate posts.