0

There are bajillion places where start command is mentioned used like

start command arguments...

and I am almost sure it worked for me, but now when I try it it wants to be called like

start title command arguments...

and indeed when I run it as

start "c:\Program Files (x86)\PSPad editor\PSPad.exe"

it opens a terminal window with title "c:\Program Files (x86)\PSPad editor\PSPad.exe" and when I add parameters like

start "c:\Program Files (x86)\PSPad editor\PSPad.exe" foobar.txt

it complains that "Windows can't find 'foobar.txt'".

Has it changed or are there two versions of it or what is going on?

  • Using windows 8 and running start /? shows title should be optional. – rob Apr 10 '14 at 10:22
  • same on Win 7, optional – Shevek Apr 10 '14 at 10:33
  • Can you specify your OS? I just tested it in windows 7 myself, and although the help does not say it is optional, typing start cmd opens a new cmd window as expected. If you receive an error, please tell us the exact error. – LPChip Apr 10 '14 at 12:03
  • @LPChip: Windows 7. – Jan Hudec Apr 10 '14 at 12:24
  • 2
    Maybe it's the quotation marks around the command? I.e. if they're there, it's assumed to be a title? – Daniel Beck Apr 10 '14 at 12:33
4

As I remember, it works this way only. So to run a command with space in a command window with title:

start "" "command with space" -option

If you want a title, you need to specify it in first set of quotes.

The explanation to this behavior is although the title is optional argument, but it is also the first argument(if used) to the start command, so if you specify a quoted string as first argument, it takes it as title.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.