I use this txt editor which does not properly handle unicode file names
In file types txt I have set up the open command to be:
...uedit32.exe "%1"
I want to use
...uedit32.exe {filepathshort}
but dopus does not substitute the short path name here, instead ultraedit tries to open a file called {filepathshort}
If I define a toolbar button I can use {filepathshort} but I really want to change the open txt file action.
Anyone know how to do this?
I guess you can try that:
uedit32.exe %~s1
It normally uses short names...
That works for the filename but the path needs to be short as well
oh, my mistake, i thought it was everything short....
well, i guess this should work:
dopusrt.exe /cmd ...uedit32.exe {filepathshort}
normally dopusrt is recognized alone, but as it will probably be stored in the registry (depends if it's DOpus or system file types), i'm not sure dopusrt can launch without the path to it.
It should work with that as dopusrt is used to launch internal opus fonctions when you normally can't...
{filepathshort} (and similar codes) are only recognised by Opus.
Generic File Type settings have to be able to work in all other programs because Opus isn't the only program that will run them.
(There are also Opus-specific File Type settings that only show up in Opus; those can use {filepathshort} etc. fine.)
Think about it:
If you change the Open verb on .TXT to use {filepathshort} and then double-click a .TXT file in Explorer, Opus isn't involved there at all. Explorer has no idea what {filepathshort} means and doesn't know that it should replace it with the name of the file you double-clicked.
Using {filepathshort} with dopusrt.exe won't work either, unless you're running dopusrt.exe from within Opus. That's because, unless it's told on the command-line, dopusrt.exe has no idea which files were selected in the program that ran it. So the filename has to be expanded by whatever runs dopusrt.exe, not by dopusrt.exe itself.
The %1 %~s1 etc. codes all work in Explorer (and Opus) and are what you have to use for File Type settings that are seen by more than just Opus.
Damn, I didn't thought about that {} are not recognised by explorer.... but of course. Hopefully for me, I haven't made any explorer type fonctions to run with this....
Alright, Takada, if you don't have your solution yet, I guess this will work:
...uedit.exe %~fs1
With that, the path should be short too
It turns out that things like %~fs1 are also not recognised by Explorer and thus not suitable for use in file type command-liness in the registry.
%1 and %L both work and are understood by Explorer but things like %~fs1 are part of the MS-DOS Batch syntax which Explorer doesn't use/support.