@PeterJones said in Is There a Way to Prevent Pasted Text from Spreading Out with Rows of Spaces?:

Or, since you said,

there aren’t any unused ones available under Plugins > Customize Toolbar

- I assume this is the one where you say, "there aren't any unused ones available". I cannot imagine that you've _actually_ enabled another couple-dozen buttons from its list, so that there are no other "available toolbar buttons", as that toolbar would be so full as to be unusable. On the other hand, that's the only thing I imagine that you _could_ mean by such a sentence.

Yes, all of the Old Large Legacy Icons are in the Current toolbar buttons box. After checking them, I decided that I might use all of them in the future.

Well, with all of that said, thanks for being patient and hanging in there through all of this. I have everything working, including adding a new icon to the toolbar. And thanks for the updated scripts.

I hope this thread serves many others.

Hi, @b, @peterjones, @coises and All,

Let’s consider the Spanish word comparación and its various forms below, pasted in a new tab :

comparación cömparÅciõn ＣömꝕarÅcⓘoñ ȻOℳₚA⒭ⱯℭᴵꝊᵰ ƆºᶆⱷǞℝȺꜿᵼᴓɲ ɕƢꟽⓟǻꝝⱭƆⅈᴗN

Note that I have deliberately exaggerated the shapes and modified the case of the possible characters !!

If you do any of the six N++ searches, below, against the six lines in the new tab, you’ll see that ONLY the two first regexes, which refer to standard equivalence clases, can find all the lines.

SEARCH (?=[[=c=]])\X(?=[[=o=]])\X(?=[[=m=]])\X(?=[[=p=]])\X(?=[[=a=]])\X(?=[[=r=]])\X(?=[[=a=]])\X(?=[[=c=]])\X(?=[[=i=]])\X(?=[[=ó=]])\X(?=[[=n=]])\X

SEARCH (?=[[=c=]])\X(?=[[=o=]])\X(?=[[=m=]])\X(?=[[=p=]])\X(?=[[=a=]])\X(?=[[=r=]])\X(?=[[=Å=]])\X(?=[[=c=]])\X(?=[[=i=]])\X(?=[[=õ=]])\X(?=[[=n=]])\X

SEARCH (?=[[=Ｃ=]])\X(?=[[=ö=]])\X(?=[[=m=]])\X(?=[[=ꝕ=]])\X(?=[[=a=]])\X(?=[[=r=]])\X(?=[[=A=]])\X(?=[[=c=]])\X(?=[[=ⓘ=]])\X(?=[[=o=]])\X(?=[[=ñ=]])\X

SEARCH (?=[[=Ȼ=]])\X(?=[[=O=]])\X(?=[[=ℳ=]])\X(?=[[=ₚ=]])\X(?=[[=A=]])\X(?=[[=⒭=]])\X(?=[[=Ɐ=]])\X(?=[[=ℭ=]])\X(?=[[=ᴵ=]])\X(?=[[=Ꝋ=]])\X(?=[[=ᵰ=]])\X

SEARCH (?=[[=Ɔ=]])\X(?=[[=º=]])\X(?=[[=ᶆ=]])\X(?=[[=ⱷ=]])\X(?=[[=Ǟ=]])\X(?=[[=ℝ=]])\X(?=[[=Ⱥ=]])\X(?=[[=ꜿ=]])\X(?=[[=ᵼ=]])\X(?=[[=ᴓ=]])\X(?=[[=ɲ=]])\X

SEARCH (?=[[=ɕ=]])\X(?=[[=Ƣ=]])\X(?=[[=ꟽ=]])\X(?=[[=ⓟ=]])\X(?=[[=ǻ=]])\X(?=[[=ꝝ=]])\X(?=[[=Ɑ=]])\X(?=[[=Ɔ=]])\X(?=[[=ⅈ=]])\X(?=[[=ᴗ=]])\X(?=[[=N=]])\X

In constrast to the last release of the Columns++ plugin, independant of Scintilla and doing true UTF-32 searches, which is able to match the six lines of our example, whatever the regex used among the six regexes above !

This example clearly demonstrates that it’s possible to perform a search without considering case and/or accentuated characters with the v1.3.1 release of Columns++ plugin ;-))

Best Regards,

guy038

@Murray-Sobol-1 said in Idea of a new installation routine:

@PeterJones said in Idea of a new installation routine:

No one should ever download a 32bit installer for modern OS. For any app. (Modern OS don’t come in 32-bit versions anymore, so I don’t understand why apps still bother distributing the 32-bit versions)

I agree with the above statement, however when I ask for an update by clicking Downloads I see this section:
Download 32-bit x86
Installer | GPG Signature
Portable (zip) | GPG Signature
Portable (7z) | GPG Signature
Mini-portable (7z) | GPG Signature

Why is this even being distributed anymore??

Because my statement was just my opinion, and not everyone agrees with it. Because there are some people who mistakenly think they need a 32-bit even though they have a 64-bit OS. And there are some people who have some unmaintained plugin that only comes in 32-bit (*). And because the developer has never decided to cut off those poor, unfortunate souls.

(*: aside: anytime I come across someone like that, I do a bit of research to help them find an alternative, or find someone who has done an unofficial recompile of the plugin for 64-bit. there are very few public plugins that have no 64-bit version and no alternative)

But that’s why we lobbied to put the 32-bit below the 64-bit, so the 64-bit gets the prominence it deserves – and why I rejoiced when it happened. Someone downloading N++ for the first time will see the 64-bit first, and will likely download that. Someone updating N++ should use the menu or auto-update, and never have to go back to the website.

@rdipardo ,
Thanks for pointing out the Native AOT template — I wasn’t aware of it when I started the ARM64 migration.

I did actually try Native AOT early on, but ran into two issues: the export limitations you mentioned, and the resulting DLL size (~57 MB), which felt way too large for a Notepad++ plugin. That’s why I ended up going with DNNE — the plugin DLL stays small (~1 MB), though it comes with the .NET 8 runtime dependency.

How large are the DLLs you’re getting with the Native AOT template? Has trimming improved enough to bring the size down to something reasonable for a plugin?

@Lionel-Lagarde said in C++11 raw string literal syntax hightlighting:

Is it true or something went wrong the last time I updated notepad++ (it already happen, my global styles are modified and the update process failed to merge the two styles)?

Nothing went wrong. Just nobody has pointed out to the developer that the entry for name="STRINGRAW" styleID="20" should be added to the stylers/themes.

If you want to add it yourself,

Exit Notepad++ app completely If you are using a theme other than stylers.xml, check if you have a copy in %AppData%\Notepad++\themes\ – if not, copy from C:\Program Files\Notepad++\themes\ to the AppData path (create the themes folder if needed) you don’t want to edit the copy in the installation directory, because your next update will just lose that Open Notepad++, and edit either %AppData%\Notepad++\stylers.xml or %AppData%\Notepad++\themes\<YourThemeHere>.xml Search for name="cpp" Add in the following line, picking whatever color you want (maybe something similar to the STRING or CHARACTER color, but it’s up to you; my example was based on the same as the default stylers.xml STRING color, but added slightly more red to the grey tint):<WordsStyle name="STRINGRAW" styleID="20" fgColor="A08080" bgColor="FFFFFF" fontName="" fontStyle="0" fontSize=""></WordsStyle>

With that, I can get Notepad++ to highlight the raw string literal:
ac9d31fb-d5e5-459a-82ad-34b57b240c3b-image.png

If someone (like you) were to put in an official feature request (checking if one exists first; if it already does, upvote it, and put a link here), it wouldn’t be hard for a interested contributor to work up a quick PR to add that missing style to the stylers/themes for a future version of Notepad++. (And with N++ now automatically adding missing styles to your local themes the next time you update, it would be made available to everyone.)

@Vitalii-Dovgan said in NppExec Manual: CHM vs. HTML version [poll]:

Somebody, stop me! It has been 2 weeks I’ve been updating and improving the HTML form of the Manual!

Sorry, it is not possible for me to stop someone from improving documentation. ;-)

@Deepa-Asthana
Before anyone can offer some ideas you will need to expand your description of the problem.

Like how many tabs open. How big are some of the files/tabs. What are your backup settings. It seems that your problem has existed before the latest update, correct? Provide the details of your installation using the ? menu option, copy and paste here. There is a FAQ post to help you. Sorry writing on phone so can’t easily provide the link.

Terry

@Carlos-Sánchez said in [New plugin] Smart Math:

I’m a bit lazy and haven’t got a clue

I can’t solve the first part, but for the clue:

it’s just a PR to the nppPluginList project. Since you’re working in GitHub already, I assume you know how to do the PR fork the nppPluginList repo, create your own branch in that branch, edit pl.x64.json to link to the 64-bit version, and pl.x86.json to link to the 32-bit version the id required in the JSON is just the SHA256 hash, which GitHub provides for you:
fd4a838f-9724-477d-b755-24836141dc88-image.png once you have edited both files in your branch, submit the PR from that branch

I’ve been footling around with my plugin a bit to try and generate a PR automatically when a new version is released. So - is the layout of the json files significant.

Most of the entries look like

\t\t\t{ \t\t\t"folder-name": "Linter++", \t\t\t"display-name": "Linter++", \t\t\t"version": "1.0.3.0", \t\t\t"npp-compatible-versions": "[8.7.5,]", \t\t\t"id": "F56573351010B62BFC75039725496C8687D53E82A3F47074F1F1B629A37A92C1", \t\t\t"repository": "https://github.com/ThosRTanner/notepad-pp-linter/releases/download/1.0.3/plugin_dll_ARM64.zip", \t\t\t"description": "Allows realtime code check against any checkstyle-compatible linter: jshint, eslint, jscs, phpcs, csslint, and many others.", \t\t\t"author": "Tom Tanner", \t\t\t"homepage": "https://github.com/thosrtanner/notepad-pp-linter" \t\t\t},

So I thought i could do my updater in python, just load up the json file, modify my entry, and dump it back, then commit

One entry (just one) uses spaces instead of tabs.

So my question is is there an official layout for these files? Is any valid json permissible (all on one line for instance), or is it expected to be formatted as 1 line per key and indented with tabs?

Would converting those spaces to tabs as part of my PR be frowned upon, or should I just read the file and modify the lines appropriately?

@KelltimeOG
Fixed in https://github.com/notepad-plus-plus/wingup/commit/5d89e486a5cb63251b8ed0b0e9f441a9774709ff
The fix will be in WinGUp v5.4.1, which is included in Notepad++ 8.9.3 release.