@waskoma said in Cant change cursor color, and latest version shortcut to start batch file claims it cant find it:

<Command name="Wikipedia Search" Ctrl="no" Alt="yes" Shift="no" Key="87"> c:\64start.bat $(FILE_NAME) $(NAME_PART).prg &quot;$(CURRENT_DIRECTORY)&quot;</Command>

I cannot replicate the problem (so far)

content of c:\64start.bat:

@echo ran command `%0 %*` @pause

content of shortcuts.xml entry:

<Command name="Waskoma Command" Ctrl="no" Alt="yes" Shift="no" Key="87">c:\64start.bat $(FILE_NAME) $(NAME_PART).prg &quot;$(CURRENT_DIRECTORY)&quot;</Command>

I tried with two files each, once with v8.4.1 and once with v8.9.2.

For ...\FileNameNoSpaces.txt:

v8.4.1 results: ran command `"C:\64start.bat" FileNameNoSpaces.txt FileNameNoSpaces.prg "C:\usr\local\apps\npp\npp.8.4.1.waskoma"` Press any key to continue . . . v8.9.2 results: ran command `"C:\64start.bat" FileNameNoSpaces.txt FileNameNoSpaces.prg "C:\usr\local\apps\npp\npp.8.9.2.waskoma"` Press any key to continue . . .

For ...\File Name With Spaces.txt:

v8.4.1 results: ran command `"C:\64start.bat" File Name With Spaces.txt File Name With Spaces.prg "C:\usr\local\apps\npp\npp.8.4.1.waskoma"` Press any key to continue . . . v8.9.2 results: ran command `"C:\64start.bat" File Name With Spaces.txt File Name With Spaces.prg "C:\usr\local\apps\npp\npp.8.9.2.waskoma"` Press any key to continue . . .

So both worked for me, and Notepad++ had no trouble running the 64start.bat, whether in v8.4.1 or v8.9.2

However, this works on the assumption that there wasn’t really the newline before c:\64start.bat in your XML. It shouldn’t matter, but it also shouldn’t be there; so if there is the extra newline, delete it.

Also, my test works on the assumption that your 64start.bat will do the “right thing” with spaces in the filename without quotes, which I am highly dubious of. My working theory is that the problem is actually either the missing quotes, or something that’s being called inside your batch file.

Notepad++ has been undergoing changes in which XML reader library it is using for parsing the config files like shortcuts.xml… so if you’ve actually got that newline, or if you have more entities than &quot; which you haven’t told us about, it might be behaving differently between the two, and that might explain the difference in behavior.

As an experiment, if removing the newline wasn’t enough to fix it, you might want to try renaming your 64start.bat and putting in a new version that’s got my contents. If it properly runs and gives similar results to what I showed in my experiment, then the problem is likely the quoting. If it doesn’t properly run, even though you are using the same <Command...> entry, then I am betting you edited your command entry before posting it here, and whatever you edited out is the culprit.

@PeterJones yes, many thanks : global override was the cause
now all highlighting is correct as set/wanted
best regards, Guy

@Gerard-Kiekens said in Notepad++ VERY slow to open:

I agree with you that the size should not change, but it did.

Hard to argue my side cogently when you provide no data.

Editing a fresh Darkmode_Default afterwards solved the problem. This one also increased in size, but kept working as fast as it should.

But not from 220kB to 500MB.

If you want to "play"with it, you can find it here:
https://www.key-can.nl/Info/DarkModeDefault.xml

The file you linked there is only about 220kB as well. And the reason it’s a different size than the actual DarkModeDefault is because it obviously started from an old version of Choco.xml, as evidenced by the copyright notice starting:

<?xml version="1.0" encoding="Windows-1252" ?> <!--// choco Copyright (c) 2008 Fabio Zendhi Nagao <http://zend.lojcomm.com.br/>

I can tell it’s an old copy of choco, though, because it is still “Windows-1252”. That was changed to UTF-8 in v7.9.3 from 2021.

DarkModeDefault was originally derived from Zenburn.xml, since the time it was created (it started with the full zenburn preamble, but eventually pared it down to

<!-- Dark mode default style for Notepad++. This file is based on Zenburn them (zenburn.xml) License: GPL2 -->

As you will probably know you can find the themes in %users%\Appdata\Roaming\Notepad++\Themes

That’s where you find your customizations. The originals (kept up to date with each update of the program) are in c:\program files\Notepad++\themes. Historically, Notepad++ would just leave your customized themes completely alone, so they would never show you any of the new styles that had been added/enabled over the last 5 years; in the recent Notepad++ releases (starting in v8.8.9, though I recommend skipping 8.8.9 and 8.9.0 and going directly to 8.9.1-or-newer because of bugs in the first two releases of this feature), it will add any missing styles or missing languages to your active theme, so that way, your Style Configurator will allow you to edit colors for new styles or languages without losing all your old theme customizations.

So the small size difference between your Choco-based theme and the actual DarkModeDefault can be explained by being based on the old Choco. The huge 500Mb size that you reported from earlier cannot be explained by anything that’s been said yet, and I still don’t understand how it could have happened inside Notepad++. And without a hint as to what the edited XML looked like for the super huge file, there’s really no way that mystery will ever be solved.

@Tangfolio ,

From a Windows command line, to pass a filename with spaces to an application, you need to put quotes around the filename. This is the way that Windows defines the command-line interface, and not something specific to Notepad++

update: sorry, that was an abbreviated response. Real life interrupted, so I posted what I had so far, at the time. continuing where I left off:

So, from the command line, notepad++.exe word1 word2.txt would try to open word1 and word2.txt in the current directory, which presumably don’t exist, whereas notepad++.exe "word1 word2.txt" would properly try to open the file with spaces in the name.

If you are using the right-click context menu in Explorer, the normal Edit with Notepad++ (which gets added via NppShell.dll, when you do a normal Notepad++ installation), then it should handle the spaces just fine. But if you created your own Notepad++ entry using regedit or a registry .reg file, you have to make sure that your entry says, "c:\Program Files\Notepad++\notepad++.exe" "%1", with the quotes around each, otherwise it will behave as you described.

Again, requiring the quotes around the filename is just the way Windows OS has defined the command-line interface (but similar is true in other operating systems, as well, because any OS must be able to tell the difference between program file1 file2.txt trying to work on two different files and program "word1 word2.txt" trying to work on one file with a space in the name.)

@waskoma said in Cant change cursor color, and latest version shortcut to start batch file claims it cant find it:

while we’re at it, some years ago probably it was you helping me to get code folding working I want to use:

;blockbegin
;blockend

but that doesnt work again, looking at it at 8.9.2 it seems to recognize it only when there are like above right in the next row to eachother.

allow folding of comments is checked. comment line is set to “,”

line comment position is allow preceding white space

I am quoting and replying to this here, because this is where it belongs:

It still works for me in v8.9.2, using the same color descriptions as I used three years ago:

1ad97c38-63dc-49e1-8e73-4cd67f843f79-image.png

60c23da2-7e57-428c-a3dc-bdcbb8861f3f-image.png

If you think you have text that doesn’t work with that, click the </> button in the forum, and paste that text between the ``` lines

update: note that 8.9.2 actually has some bugs with regards to entering keywords: it would crash on long keywords. And, if my experiences just now were any indication, it also doesn’t necessarily save the edits to other fields, like the open/close for the folding or comment-line fields. But when I tried the bugfix build for my #17520 issue report, it allowed me to enter those other fields, and save them. So if you’re editing UDL, I actually recommend v8.9.1, not v8.9.2 (until the v8.9.3 is released with a fix)

@Mario-Korva

Finally I found some time to try to fix C++ Function List parser regex (cpp.xml) to show all constructors.
Modification of the mainExpr in the <classRange> element of <parser>:

Original expression:

mainExpr="(?x) # use inline comments ... )? \s* # trailing whitespace \{ # class/struct body "

Modified expression:

mainExpr="(?x) # use inline comments ... )? \s*(:[^:]*)? #<- trailing whitespace and initializers \{ # class/struct body "

I did equivalent modification of the mainExpr in the <function> element of <parser>. This modification enable that function list shows constructors with initializers.
I found also that functions defined with the call convention keyword, for example:

void __fastcall function(parameter) { ...

are also missing in the function list. This is solved with the addition of the

(__[\d\l]+\s+)? #<- call convention __fastcall, __stdcall, etc.

immediately after second “# type pointer/reference” part of mainExpr in the same two elements.

After this modificatoins the Function List of my C++ source files appears complete! I hope that I didn’t break something.
I tried to include modified cpp.xml here, but the post becomes too long.
I hope this will be useful for someone.