[Solved] How to pass a parameter with a space (e.g. file name) ?

[aequilibris]

The next cmd command successfully opens a file in the right panel of TC:

Code: Select all

start /b cmd /c "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R=PATH

It works, provided that the PATH does not contain spaces. How to get the command work for a path, which contains spaces ? The use of "PATH" or 'PATH' does not work, as well as other typically used tricks. Is there any solution ?

[Ovg]

add C:\Program Files (x86)\totalcmd9 to you PATH environment variable and

Code: Select all

start /b cmd /c TOTALCMD64.EXE /O /R="PATH"

will work

[aequilibris]

I shall try that as a last resort (even if it is unclear, why it should work). However still, is it possible to avoid to use environment variables ?
Moreover, would the next variant work ?

Code: Select all

start /b cmd /c TOTALCMD64.EXE /O /L="PATH1" /R="PATH2"

UPD. Thank you Ovg, I tried your method. It works, also for the variant with PATH1 and PATH2. Still, is it a way to do it without the environmental variable ?

[Ovg]

Environmental variable Path already exist in your system (whether you want it or not and not only in your). Why not using it?

[Stefan2]

Is there a reason why you use start AND cmd ?
I never use that and do not get the benefit.

and
To avoid problems with spaces in your PATH, quote that like "PATH".

But since you call two interpreter (start.exe and cmd.exe) me guess one or each of them remove the outer quotes,
so try to double the quotes,... maybe smtg like
start /b cmd /c " "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH" "



Don't know for sure.

EDIT:
please note that START.exe use the first quoting for the window title,
I don't know if that is still true for smtg like your nested code:
start /b cmd /c "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"
but maybe just try
start "" /b cmd /c "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"




 

[Dalai]

But since you call two interpreter (start.exe and cmd.exe) me guess

There is no start.exe. START is an internal command of CMD.

Nevertheless you're right about the quoting and the weirdness of using START to call CMD itself, and it gets stranger when you know that START is an internal command (so CMD essentially calls CMD, which is ... uhm... superfluous).

Regards
Dalai

[aequilibris]

Environmental variable Path already exist in your system (whether you want it or not and not only in your). Why not using it?

It is just unnerving that I could not pass a parameter in quotes without resorting to the method above, i.e. by removing the quotes in an other path. It works, but why ? It does not seems logical. The initial syntax should have worked. In any case, thank you, Ovg, for your practical proposal.

Is there a reason why you use start AND cmd ?

Just my ignorance. Once I have composed a working line from directives, which I picked up, and while it is working, I do not change it . Indeed, the same line works without the "start /b" header.

To avoid problems with spaces in your PATH, quote that like "PATH".
...
start /b cmd /c " "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH" "

I am quite ignorant in this area, but I do believe that start does not interfere in terms of parsing of the subsequent expression by cmd (as pointed out by Dalai). If I remove "start /b" everything behaves similarly. However, to my utmost surprise, your method of using doubly nested paths is working !

Code: Select all

cmd /c ""C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH""

I do not know why it is so, but at least this trick has a general value for me, as it shows the way to "force" the passing of the parameters in such cases.

Thank you very much, Stefan2.

[Hacker]

aequilibris,

Code: Select all

"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O "/R=PATH"

Code: Select all

"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"

both work completely fine here.

Roman

[aequilibris]

Code: Select all

"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O "/R=PATH"

Code: Select all

"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"

Roman, unfortunately neither case is working. I have just checked. Moreover, the second case was the one, I have reported as not working right in the first message.

[Dalai]

2aequilibris
One really important thing about the START command: The first quoted parameter it sees is taken as a window title for the newly created process! That's why it works without quoting anything, and it doesn't when quoting a parameter. I'm sure there are examples on the internet that take this behavior into account and use something like

Code: Select all

start [/wait] "" "command with spaces.exe"

or with a title

Code: Select all

start [/wait] "useless title" "command with spaces.exe"

or similar.

Another thing: Why use CMD at all

Code: Select all

cmd /c ""C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH""

?
This should work the same:

Code: Select all

"C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"

And it even has the advantage of not opening a CMD window at all (and avoid "flashing" of such window).

Regards
Dalai

[Usher]

Another thing: Why use CMD at all

Try to autostart some program minimized using entry in registry key HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

For example add entry for task manager:

Code: Select all

start "" /min C:\WINDOWS\system32\taskmgr.exe

[Dalai]

Try to autostart some program minimized using entry in registry key HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

How does CMD itself help with that? The START command can do that (start /min), but CMD without START can't and doesn't. Apart from that, I'd rather use something like NirCmd or Cmdow, or use an LNK file with minimized flag in the start menu.

The command line my question was about didn't use the START command, that's why I asked why CMD use at all. And, BTW, I don't think this is about autostart (but I might be wrong).

Regards
Dalai

[aequilibris]

2aequilibris
One really important thing about the START command: The first quoted parameter it sees is taken as a window title

I guess, if there is one. In any case, I have tested the previous examples also without the start command. I have found no difference with the shortened version, i.e. starting with cmd. It seems, that the use of start cannot be held responsible.

Another thing: Why use CMD at all

Dalai, thank you for educating me on this point. I had a feeling that one need a kind of 'executing directive'. However, it is superfluous and indeed, your version is working. Still, sometimes, it is nice to use command keys, e.g. with cmd, and good to know a method to pass the parameters, even if they contain spaces.

P.S. I am sorry for repeatedly demonstrating my ignorance regarding knowledge of Window's command prompt. However, I am very grateful for all your answers, and may be that thread will be useful for someone like me.

[Hacker]

aequilibris,

Moreover, the second case was the one, I have reported as not working right in the first message.

I know, I am just saying it works fine here, so there must be a problem elsewhere (not with the syntax itself).

Roman, unfortunately neither case is working. I have just checked.

Can you perhaps create a video of what is happening?

Roman

[aequilibris]

To Hacker: I am not sure, whether it is even worth to mention, but when I execute a .bat file with

Code: Select all

cmd /c "C:\Program Files (x86)\totalcmd9\TOTALCMD64.EXE" /O /R="PATH"

the cmd window returns me

Code: Select all

'C:\Program' is not recognized as an internal or external command, operable program or batch file