You’re welcome, @Inshita-Rawat. If you follow the links in the FAQ, especially to one of the try-it-live websites, like regexr.com (*), they will explain the individual elements of the regular expression in great detail.

*: I usually use regexr, and switch it from “JAVASCRIPT” to “PCRE” in the upper right. PCRE comes come close to Notepad++'s Boost-based regular expressions — since both Boost↗ and PCRE↗ are based on Perl regular expressions, though there are differences (both from each other, and from Perl).

If you paste my ^(.*?) (\d.*) regular expression into regexr.com with PCRE, and FLAGS=global,multiline (/gm), along with example data – see https://regexr.com/466oe – you can see the explanation, or by clicking on REPLACE, you can input my replace string, and see what it will become.

hi how are you

Hey @Meta-Chuh and @guy038,
that’s some great news you sharing. I certainly will look into this.
Thanks for the quick help.

Best regards.

@Alan-Kilborn said:

editor.styleSetBack(STYLESCOMMON.LINENUMBER, (255, 0, 0))

will turn the background of the line-number margin a rather glaring red, for example.

Yes, changing the line number color is actually better solution in general and it can be better visible.
I’ve used folder margin from the beginning and just was too lazy to experiment further :)
BTW, if you want to make permanently visible folder margin in any file, it can be done with Pythonscript plugin via “startup.py” script.

Disable folder margin:
Settings - > Preference -> Editing : set “Folder margin style” to “None” Add e.g. this to startup.py: editor.setMarginWidthN (2, 16) # set folder margin to 16 pixel editor.markerDefine (MARKEROUTLINE.FOLDEROPEN, MARKERSYMBOL.ARROWDOWN) editor.markerDefine (MARKEROUTLINE.FOLDERSUB, MARKERSYMBOL.EMPTY) editor.markerDefine (MARKEROUTLINE.FOLDERTAIL, MARKERSYMBOL.EMPTY) ...

then Restart Npp. So can even define custom marker symbols or just set them all to EMPTY.
see:
https://www.scintilla.org/ScintillaDoc.html#Markers
http://npppythonscript.sourceforge.net/docs/latest/enums.html#markeroutline

@SinghRajenM said:
I do not have such an error

@KOMN-W said:

I am having trouble with notepad++

But you didn’t say anything about the trouble you’re having with Notepad++!

@PeterJones

since two of the forum’s python experts are not actively helping here anymore, I need to up my PythonScript output …

i really wished there was an easy way to lure both back somehow … for example with a complementary free cake for all returning members 🥧🍰🎂 :D

i’ve still got the hope that someday maybe one or both will return for either historic, good times reasons, or 'cause you lured them back with future’s most ultimate py guru knowledge 👍
(ps: no pressure, i think your py is already pretty good and way better than eg. mine)

reader’s note:
this was slightly off topic, so i give my sincere apologies to everyone in advance.

@guy038 said:

Thanks @guy038 you are a star. I misread and thought everything needed to be on a single line. You new regex works perfectly.

Sometimes instead of UTF-8 it defines windows-1258

Alan, Thank You for your answer!

@guy038

there’s more than that broken with the current auto detection !
same vietnamese detection happens if you save the word “Réservation” to a new utf-8 file and reopen,

so only the combination of ï and é in the same document is detected correctly, é only will detect it as vietnamese

this did not happen prior to this commit that @Eko-palypse mentioned.

You may, also, convert your file to the UTF-8-BOM encoding

this is not possible in many cases, because those files like in this case are in an open source repository.

same with spanish, exept if i have an ñ in my documents, so i didn’t notice it before, as most of them have an ñ.
german characters work ok so far.

I am using Autohotkey, and what worked for me is adding an ‘$’ before the hotkey as in ‘$^v::’ (Ctrl+v). Read about the prefix ‘$’ here: https://www.autohotkey.com/docs/Hotkeys.htm