DosTips.com

m " the Computer History Museum is pleased to make available the source and object code to Microsoft’s MS-DOS operating system versions 1.1 and 2.0, for non-commercial use. The zip file contains four subdirectories: v11source: 7 assembler code files, and an explanatory email from Tim Paterson v...

[quote="operator] Guys, @jeb showed me link how the CMD.EXE parses nearly everything. I hope it helps: m [/quote] I'm aware of jeb and dave benham's posts on the batch parser at that link, but I couldn't find the answer there, so maybe I am not looking at the right thing there. I know they cont...

First, cmd.exe searches for unescaped and unquoted "&|><" characters. If any found, they are specially treated. Second, it expands all %variables%. Third, cmd.exe removes all unescaped and unquoted carets. Fourth, it splits "%*" into "%1 %2 %3...". This is all I wo...

You don't understand: it's because argument count isn't changing with call , but it could be so if unescaped delimiters were allowed. One less caveat with call is always better. And it's eating the caret cause argument split phase is done after normal parsing phase, otherwise set "a=b c" ...

The batch methods all cheat to an extent and use javascript.. there's no other way in "batch". if you're willing to go towards 3rd party but commonly used linux tools, but without leaving all the functionality to some linux tool for example, get a linux tool called xxd which puts the file ...

so it'd be safer if del file^ * behaved like del file" "* rather than it being interpreted as del file * deleting the file "file", and prompting re deleting all files in the current directory. Why are you in defense of the less safe option? And as to echo not caring about delimit...

Good findings. So caret works in the path part where the path is a full path but doesn't ever seem to work in the arguments.

"a b.bat" has @echo %1

Ctrl-V to paste. PFFFT (and right click aside).. Use unxutils pclip (that pclip line is a joke by the way.. though it can be a useful tool , and not well known)

C:\>c:\a^ b\a.bat<ENTER> it runs a.bat I know cd a b works, CD is clearly taking all parameters to it as one parameter. But I notice that C:\>c:\a b\a.bat <ENTER> <-- doesn't run "c:\a b\a.bat" it understandably, says c:\a is not recognized as an internal or extenal command. That tells me ...

yeah the workarounds I mentioned are easy.

Initially I thought this might be a fundamental thing about CMD and if so then I wanted to get to the bottom of it by posting here.

Now I know it's not, and it's Ming GCC behaviour

what makes you think ming gcc emulates bash or uses dlls of bash?

He is referring to a shell(probably bash) within Windows within Ming. No, not probably. He is definitely referring to bash when he said "Bourne" and linked to the manual. OK I didn't spot that. Anyhow, no i'm not using Bourne. If I was using Bash or Bourne then I wouldn't have a C:\> I'd ...

I am using CMD.EXE not the MinGW command shell (I'm not sven sure there is such a thing? do you mean `C:\MinGW\msys\1.0\bin\bash.exe`? ) I am not using bash.exe I am using cmd.exe Penpen made it pretty clear he was referring to bash. BASH = Bourne Again Shell He is referring to a shell(probably bas...

I am using CMD.EXE not the MinGW command shell (I'm not sven sure there is such a thing? do you mean `C:\MinGW\msys\1.0\bin\bash.exe`? ) I am not using bash.exe I am using cmd.exe I'll add some more info. When c:\perl64\site\bin is not in the path, and the curent directory is c:\mingw\bin then no fu...

I do not understand this I have two gcc.exe files they are both different. I guess i'll try to explain what I might expect.. though what I expect is all wrong and then perhaps those here can enlighten me as to why this is happening C:\MinGW\bin>set path=.;c:\windows\system32;C:\Perl64\site\bin C:\Mi...