Start menu: %temp% in Parameters causes %T (target)
Moderators: white, Hacker, petermad, Stefan2
Start menu: %temp% in Parameters causes %T (target)
Well, sorry I bumped an old topic, icfu suggested I'd make a new topic, so here it is:
I want to make an item in the start menu that parses the selected items as a m3u playlist to foobar2000. For foobar200, this can simply be done by "foobar2000.exe playlist.m3u" as commandline.
Now because foobar2000 will not recognize the extension .tmp of the "%L" file list (it could directly be used as a playlist for that matter), I wanted to make sure it's renamed to playlist.m3u. This should be done by the following I guessed:
Command: cmd.exe
Parameters: /c copy /y "%L" "%temp%\playlist.m3u" & start e:\multimedia\foobar2000\foobar2000.exe "%temp%\playlist.m3u"
So it should copy the list file to playlist.m3u in the temp directory. But what happens is that a file called "empplaylist.m3u" is created in the target directory (which should be specified as %T in Total Commander).
It doesn't matter whether I use "%TEMP%" ("%TMP%") or "%temp%" ("%tmp%").
I tried TC 6.52.
P.S. It could be a nice option to specify the extension of the list file, using something like "%L[m3u]" or "%L[txt]" as parameter, to deal with problems like this
I want to make an item in the start menu that parses the selected items as a m3u playlist to foobar2000. For foobar200, this can simply be done by "foobar2000.exe playlist.m3u" as commandline.
Now because foobar2000 will not recognize the extension .tmp of the "%L" file list (it could directly be used as a playlist for that matter), I wanted to make sure it's renamed to playlist.m3u. This should be done by the following I guessed:
Command: cmd.exe
Parameters: /c copy /y "%L" "%temp%\playlist.m3u" & start e:\multimedia\foobar2000\foobar2000.exe "%temp%\playlist.m3u"
So it should copy the list file to playlist.m3u in the temp directory. But what happens is that a file called "empplaylist.m3u" is created in the target directory (which should be specified as %T in Total Commander).
It doesn't matter whether I use "%TEMP%" ("%TMP%") or "%temp%" ("%tmp%").
I tried TC 6.52.
P.S. It could be a nice option to specify the extension of the list file, using something like "%L[m3u]" or "%L[txt]" as parameter, to deal with problems like this
2Guillaume
In "Parameters" you cann't use environment variables directly. In your case double % would help.
In "Parameters" you cann't use environment variables directly. In your case double % would help.
change this toParameters: /c copy /y "%L" "%temp%\playlist.m3u" & start e:\multimedia\foobar2000\foobar2000.exe "%temp%\playlist.m3u"
Code: Select all
Parameters: /c copy /y "%L" "%%temp%%\playlist.m3u" & start e:\multimedia\foobar2000\foobar2000.exe "%%temp%%\playlist.m3u"
The doorstep to the temple of wisdom is a knowledge of our own ignorance. Benjamin Franklin
Long time ago, but I have the same problem here and it is not working with a double percent sign.
I want to call a Autohotkey-Script from %APPDATA%\GHISLER\Scripts folder.
After adding a start menu entry with the command "%APPDATA%\GHISLER\Tools\Autohotkey\AutoHotkeyU64.exe" (this works) I tried the following parameters with this results:
"%APPDATA%\GHISLER\Scripts\myscript.ahk"
Script file not found
{SOURCE PATH}\PPDATAGHISLER\Scripts\myscript.ahk
"%%APPDATA%%\GHISLER\Scripts\myscript.ahk"
Script file not found
{SOURCE PATH}\%APPDATA%\GHISLER\Scripts\myscript.ahk
What is the problem?
Thanks a lot in advance.
Kind regards,
tresi
I want to call a Autohotkey-Script from %APPDATA%\GHISLER\Scripts folder.
After adding a start menu entry with the command "%APPDATA%\GHISLER\Tools\Autohotkey\AutoHotkeyU64.exe" (this works) I tried the following parameters with this results:
"%APPDATA%\GHISLER\Scripts\myscript.ahk"
Script file not found
{SOURCE PATH}\PPDATAGHISLER\Scripts\myscript.ahk
"%%APPDATA%%\GHISLER\Scripts\myscript.ahk"
Script file not found
{SOURCE PATH}\%APPDATA%\GHISLER\Scripts\myscript.ahk
What is the problem?
Thanks a lot in advance.
Kind regards,
tresi
You can only use %%-enclosed envvars in parameters field if target application supports them (because they are passed as is), and it seems that AutoHotkeyU64.exe doesn't expect envvars there.
You can pass script in command field, e.g.:
You can pass script in command field, e.g.:
Code: Select all
Command: "%APPDATA%\GHISLER\Tools\Autohotkey\AutoHotkeyU64.exe" "%APPDATA%\GHISLER\Scripts\myscript.ahk"
Parameters: <other parameters>