@Andrej730 said in Notepad++ font with emoji support / Segoe UI Emoji slows down notepad++:

Hi! I was looking for a way to show emojis in notepad (similarly to https://community.notepad-plus-plus.org/topic/20642/) and I’ve found it, it requires enabling DirectWrite in preferences (it seems nay DirectWrite option works for it) but it also requires a special font that supports emojis.

There are lots of fonts that support emojis

The font I’ve found for it Segoe UI Emoji - which works but the problem is that using this font slows down notepad++.

The font itself, combined with the DirectWrite settings, might be the culprit. When I tried the experiment with DirectWrite (default) and Segoe UI Emoji, I also saw a slowdown… But if I switch to GDI (most compatible) (and restart), then I don’t think I see the slowdown… not 100% sure. But I don’t know if that mode will show all the emojis you want, even with that font.

However, Segoe UI Emoji doesn’t appear to be a monospaced font, and Notepad++ works best with monospace.

Any suggestions for getting emojis in notepad++ by some other way or solving this problem with Segoe UI Emoji font?

Try without directwrite. Try a different font.

When I do DirectWrite (default) and my old normal DejaVu Sans Mono or my new normal FiraCode, I am able to see many emoji (even ones that those specific fonts don’t support, because of the “composite font” capability of Windows that DirectWrite enables). It’s possible that combination isn’t sufficient for you, but it’s something worth trying. I have never noticed a font-related slowdown when using those settings and fonts.

@Mark-Olson Thank you for the warning

@TG-King said in Blue icons:

but the icons were blue, and I think they were round.

Sounds like you used a set of custom icons, as per the User Manual > Config Files > Toolbar Icon Customization

That section has a link to a zip file with various icon sets, so maybe you used one of those; or maybe you found icons elsewhere, but we cannot tell you where you found them.

@Mark-Olson said in Markdown & Lint:

VSCode has a Markdown language server that I quite like; maybe you could use that.

I am afraid this is not possible because this extension uses node-ipc as a communication channel.

node-ipc: use node IPC communication between the client and the server. This is only supported if both client and server run under node.

If other LSP servers that use stdio or socket, i.e. tcp, are available, this would of course be an alternative.

@guy038 I think the OP has left. He had written “I used Blank operations-> trim trailing space and then “\d+(?=” “\d+” “\d+”$) and its fine now. Ty both for your help!”

We won’t know exactly what character(s) the trailing spaces were but now know the original issue was space characters of some sort.

In hindsight, I should have used \h* instead of * in my original proposed fix as \h matches the various horizontal space characters plus is less likely to introduce errors as people manually copy from what they read in a forum post on a screen into a regular expression.

@Samuel-Connault

One possible way to solve this is using the sort features in the Columns++ plugin.

If you want to try it, you can install that plugin from Plugins Admin. Then, select nothing if you want to sort the whole document; otherwise, select the lines you want to sort. When you select a Sort command in the next step, you’ll be prompted to allow the selection to be converted to a rectangular selection; allow it.

There are two sort options that might help. First, try the easy one: select Sort ascending (locale) from the the Columns++ menu. That might give you what you want.

If it doesn’t, a more controllable option is to select Sort… from the menu. The dialog that follows allows you to specify a regular expression that selects the sort key in each line.

Depending on how well you know regular expressions, the help link above and your knowledge might be enough, or you might need more guidance. Try first, and ask if you need more help.

Alternatively, that same dialog allows you to specify more details about the Locale sort, which might solve your problem without regular expressions even if the default locale sort does not.

@Ussene-Nicururo ,

We’re you trying to answer the original question? Or ask a new, related question? Because that’s just a bunch of example text, and does not accomplish either.

@Jim-Julian said in block comment color:

I opened the style configurator but could find reference to only single line comment text color (green).

Is there a way to change the color of python block comment text?

Thanks.

@PeterJones mentioned the (orange) triple strings. I’ll mention the (green) block comments.

The lexer does style block comment text.

https://github.com/notepad-plus-plus/notepad-plus-plus/blob/a679e8ebfb425ae4c71a34a2080dd1a9a376acd6/lexilla/lexers/LexPython.cxx#L908-L909

Python has no multiline comment like C like languages unfortunely.

/* comment can span multiple lines */

The Python lexer does have block comments if that can be defined as such.

# comment line ## old code ## old code

The ## is SCE_P_COMMENTBLOCK style which in Style Configurator described as COMMENT BLOCK. It may not be noticeable as both SCE_P_COMMENTLINE and SCE_P_COMMENTBLOCK default to same style settings.

Changed COMMENT BLOCK in Style Configurator to grey shows

pyBlockComment.png

So now more customization can be done to improve the view.

@PeterJones thank you, unfortunately that bug has been fixed, but my work is very suitable for that bug, it helps me to handle it faster because if I use the macro to add HOME, it will affect my later macros, maybe I have to live with the old version, or will use the new version with many improvements but it will be more inconvenient for me, anyway thank you, I have been waiting for your reply all day

@Coises Thanks. “Margins” is not a section I looked in. I thought it would be in “Editing” or “General.”

Interestingly (maybe?), I have found a similar issue involving Ditto and attempting to paste into the PythonScript console window; see HERE.

Hi All,

See my important and final comment about my own issue :

https://github.com/notepad-plus-plus/notepad-plus-plus/issues/16279#issuecomment-2726313083

BR

guy038

@Richard-Darwin

Most likely you are editing a file with Windows line endings, which are \r\n, not just \n.

I would suggest:

Leave . matches newline unchecked — you don’t want that .+ to cross lines

Use \R to represent the break between lines — it matches \r, \n or \r\n

You don’t need the $ when it’s immediately followed by a line-ending character, nor the circumflex immediately after (though they don’t hurt, either)

So, try: ^(.+)\R\1Ɣ$ and see if that matches as desired; leave . matches newline unchecked. If you are using Windows line endings, use \1\r\n\1=Z to replace. (On the status bar at the bottom, towards the right side, you’ll see either Windows (CR LF), Unix (LF) or Macintosh (CR), which tells you the current line ending setting for your file.)

@AlanRobbo-69 said in Fold Margin Style Box Tree:

@Alan-Kilborn
Yes.

@AlanRobbo-69 is a different username than @Francis-Robinson – are you the same person? If so, please use one account for posting, so the conversation don’t get confused.

Alan’s incredulity is that that you seem to think that Fold Margin has no purpose, just because you cannot customize it for built-in languages. That’s an interpretation that he cannot fathom. I understand it’s annoying to you, because you found a bug, but if the Lexilla library had properly implemented the right folding rules for VB, you wouldn’t think it needed to be customizable in order to serve a purpose – so I think your “cause - effect” pair of “it’s not customizable - thus, it doesn’t serve a purpose” is fallacious. You had bad data, so you came to a bad conclusion; it happens. If you wanted to say at this point, “fold margin for Visual Basic does not serve my needs, because it is currently broken” that’s completely reasonable (but a very different statement than you made). And my response to such a hypothetical statement would be, “that’s too bad; hopefully ScintillaOrg will fix Lexilla, so that Notepad++ can be updated. too; until then, I guess you won’t be able to fold, unless you cleanly indent your code; sorry.”

@Monsterray ,
In addition to what @PeterJones is saying, while you have a functional ability that he suggests, you could create your own UDL mirroring the stuff that is already accessible to you from the main language you want to copy from, like Keywords, background colors, foreground colors, font Name, font size, font style, and helpfully, the Names that the word style is applied to from the stylers.xml file, so you can duplicate it inside of the UDL with applicable mapping to the UDL components of Operators 1 & 2 and Delimiters, Comment and Number, Folding & Default and Keyword Lists. You can also then work on the Function List aspect and the AutoComplete that would be tailored to your use case and preferences. We don’t have control over the parsing and application and customization that writing the lexer does, but if you work hard enough and learn the intricacies of working with the UDL and customizable features available, you can make a pretty good alternative to the original’s capability…but it will take learning and work. :-)

The people here can help you do it, if you want to, or you can do what @PeterJones suggests to do it the easy way. :-)

Below here are the mappings from the Python section of the stylers.xml file you’ll need to map to the UDL categories and properties.

<LexerType desc="Python" ext="" name="python"> <WordsStyle bgColor="FFFFFF" fgColor="000000" fontName="" fontSize="" fontStyle="0" name="DEFAULT" styleID="0" /> <WordsStyle bgColor="FFFFFF" fgColor="008000" fontName="" fontSize="" fontStyle="0" name="COMMENT LINE" styleID="1" /> <WordsStyle bgColor="FFFFFF" fgColor="FF0000" fontName="" fontSize="" fontStyle="0" name="NUMBER" styleID="2" /> <WordsStyle bgColor="FFFFFF" fgColor="808080" fontName="" fontSize="" fontStyle="0" name="STRING" styleID="3" /> <WordsStyle bgColor="FFFFFF" fgColor="808080" fontName="" fontSize="" fontStyle="0" name="CHARACTER" styleID="4" /> <WordsStyle bgColor="FFFFFF" fgColor="0000FF" fontName="" fontSize="" fontStyle="1" keywordClass="instre1" name="KEYWORDS" styleID="5" /> <WordsStyle bgColor="FFFFFF" fgColor="FF8000" fontName="" fontSize="" fontStyle="0" name="TRIPLE" styleID="6" /> <WordsStyle bgColor="FFFFFF" fgColor="FF8000" fontName="" fontSize="" fontStyle="0" name="TRIPLE DOUBLE" styleID="7" /> <WordsStyle bgColor="FFFFFF" fgColor="000000" fontName="" fontSize="" fontStyle="1" name="CLASS NAME" styleID="8" /> <WordsStyle bgColor="FFFFFF" fgColor="FF00FF" fontName="" fontSize="" fontStyle="0" name="DEF NAME" styleID="9" /> <WordsStyle bgColor="FFFFFF" fgColor="000080" fontName="" fontSize="" fontStyle="1" name="OPERATOR" styleID="10" /> <WordsStyle bgColor="FFFFFF" fgColor="000000" fontName="" fontSize="" fontStyle="0" name="IDENTIFIER" styleID="11" /> <WordsStyle bgColor="FFFFFF" fgColor="008000" fontName="" fontSize="" fontStyle="0" name="COMMENT BLOCK" styleID="12" /> <WordsStyle bgColor="FFFFFF" fgColor="880088" fontName="" fontSize="" fontStyle="1" keywordClass="instre2" name="BUILTINS" styleID="14" /> <WordsStyle bgColor="FFFFFF" fgColor="FF8000" fontName="" fontSize="" fontStyle="2" name="DECORATOR" styleID="15" /> <WordsStyle bgColor="FFFFFF" fgColor="808080" fontName="" fontSize="" fontStyle="0" name="F STRING" styleID="16" /> <WordsStyle bgColor="FFFFFF" fgColor="808080" fontName="" fontSize="" fontStyle="0" name="F CHARACTER" styleID="17" /> <WordsStyle bgColor="FFFFFF" fgColor="FF8000" fontName="" fontSize="" fontStyle="0" name="F TRIPLE" styleID="18" /> <WordsStyle bgColor="FFFFFF" fgColor="FF8000" fontName="" fontSize="" fontStyle="0" name="F TRIPLEDOUBLE" styleID="19" /> <WordsStyle bgColor="FFFFFF" fgColor="000000" fontName="" fontSize="" fontStyle="0" name="ATTRIBUTE" styleID="20" /> <WordsStyle bgColor="FFFF80" fgColor="000000" fontName="" fontSize="" fontStyle="0" keywordClass="substyle1" name="USER KEYWORDS 1" styleID="128" /> <WordsStyle bgColor="FFFF80" fgColor="000000" fontName="" fontSize="" fontStyle="0" keywordClass="substyle2" name="USER KEYWORDS 2" styleID="129" /> <WordsStyle bgColor="FFFF80" fgColor="000000" fontName="" fontSize="" fontStyle="0" keywordClass="substyle3" name="USER KEYWORDS 3" styleID="130" /> <WordsStyle bgColor="FFFF80" fgColor="000000" fontName="" fontSize="" fontStyle="0" keywordClass="substyle4" name="USER KEYWORDS 4" styleID="131" /> <WordsStyle bgColor="FFFF80" fgColor="000000" fontName="" fontSize="" fontStyle="0" keywordClass="substyle5" name="USER KEYWORDS 5" styleID="132" /> <WordsStyle bgColor="FFFF80" fgColor="000000" fontName="" fontSize="" fontStyle="0" keywordClass="substyle6" name="USER KEYWORDS 6" styleID="133" /> <WordsStyle bgColor="FFFF80" fgColor="000000" fontName="" fontSize="" fontStyle="0" keywordClass="substyle7" name="USER KEYWORDS 7" styleID="134" /> <WordsStyle bgColor="FFFF80" fgColor="000000" fontName="" fontSize="" fontStyle="0" keywordClass="substyle8" name="USER KEYWORDS 8" styleID="135" /> </LexerType>

@leonardchai Thank you very much. I searched for your plugin in the plugin admin menu and there it was. Works great!

@Alan-Kilborn

Solved. Thanks

I just remembered similar “file does not exist” issue in the N++ v8.7.1+ caused by an interfering SW (in that case by the corporate telemetry spyware Teramind, monitoring all the files opened by user):

https://community.notepad-plus-plus.org/topic/26462/file-does-not-exist

@PeterJones @xomx
When I switched the rendering mode to “GDI (most compatible),” the font display ended up looking even stranger than before, especially with Chinese fonts. It felt like I’d been transported back 60 years.

Image
Image