Adding the file extension will also work: notepad++.exe (without quotes) works fine here
Turns out I was wrong about this. I defined a 'notepad' alias in another TCC box, but forgot it was a local alias. So, adding the file extension doesn't do the trick.
I like the beauty of simplicity/consistency, but I don't think it is possible in this case:
The most simple parsing rule would be: if not "space" before "+", the "+" is part of the filename/alias/..
But .... CMD (and TCMD) supports a command like: copy 1.txt+2.txt all.txt
(without spaces around the "+"). So it will be "messy" anyhow.
The carpet in the room is just too small to cover all the problems. If you fix the (CMD-) problems on one side of the room, you will uncover new problems on the other side of the room. And buying a complete new (handmade, expensive) carpet is not really an option.
So in this case an extra piece of the same carpet was made and put in an unremarkable corner and stitched together with a few """ ...
I can live with that (but I have to confess: I never have to be in that corner of the room :-)
On the other hand: there is some strange "+"-related behaviour:
(without a space) gives you: The system cannot find the file specified. "C:\Temp\ff\++".
- If + is not a valid filename character ([title]
), then why is echo something > "+++.+++"
supported? (Or at least warn me that I'm being stupid).
- echo something > one+two.txt needs too be quoted in TCMD, too (as expected)
Out of curiosity: what will the parser do with external commands that have command-line options like /+4 (can't think of a real scenario or a good example)
BTW: Isn't there some thread where the differences between CMD and TCMD can be logged? Couldn't find it.