in reply to Re^5: Execute by order
in thread Execute by order

...at its simplest, by changing command>/c> to <c>command &

The equivalents on Win* are:

  1. start command
  2. start command > file 2>&1
  3. start command > nul  2>&1

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP PCW It is as I've been saying!(Audio until 20090817)

Replies are listed 'Best First'.
Re^7: Execute by order
by Bloodnok (Vicar) on Aug 13, 2009 at 14:11 UTC
    TFT BrowserUk ,

    start looks familiar, but the *NIX-like re-direction syntax ? Is it/has it been recently introduced ?

    A user level that continues to overstate my experience :-))
      but the *NIX-like re-direction syntax ? Is it/has it been recently introduced ?

      No. It's been in cmd.exe for the last 16 years!

      And it(*) was in command.com for under DOS for 10 years or more before that. My memory doesn't recall whether it was a part of DOS v1.0, I think you may have had to wait until v1.25 circa. 1983.

      (*)Albeit a somewhat broken implementation that used files rather than memory for the transfer buffers.


      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
        1>file 2>file works but &1 does not
        perl -le" warn 1; print 2; " 2>&1 >one