DosTips.com

Hi, 1) Default values undefined variables are more or less empty variables, but only inside batch files. The difference for batch files and command line echo var: %undefinedVar% Output when executed on the command line: var: %undefinedVar% Output when executed in a batch file var: But even in batch ...

I found one useful behaviour for the "missing stack entry". It works nearly the same as a GOTO, but there is one difference when it's in a command block or there are appended commands. A GOTO discards the other commands of a block and all appended commands (by &) @echo off echo [%0]: Before calling ...

Hi siberia-man, thanks for the interesting link, I was able to understand the posts, thanks to google translate. You described the ? and * for labels, there both characters works as expected, like any other charcter. But the key difference is using them not in a lable, instead use them in a called f...

Hi, while refactoring my macro library, I found an unknown behaviour of the CALL/return file logic. :!: It fails when in the called batch file path at least one question mark or asterix is embedded. It seems a little bit related to the (goto) 2> nul glitch. First a sample, showing the normal behavio...

Hi sst, I'm impressed by your analysis/debugging. :o :!: It explains so much. Now, I understand why the REM trick to gather the arguments works so good, and why it fails with multiline input. The REM parser will read the first token(GeToken) and compares it against "/?". If the token is "/?" it sets...

Hi Penpen,

you are right. The Call is superfluous, I cpoied it from macro code.

@GCRaistlin
No it's not possible to use delayed expansion to replace a single bang, only when the bang is precede with other charactets.

Hi GCRaistlin, yes, but it depends on the content of your string It's simple for simple content (without quotes in the content) @echo off setlocal DisableDelayedExpansion set "string=Test with caret ^ bang ! and some other <>&| %% stuff" setlocal EnableDelayedExpansion set "_tmp=%string:!=###%" set ...

Hi pstein, it's not as easy like in bash with myVar=$(myCmd) But with the help of a macro you can simplify it to %$set% volumeName="vol D:" Or even multi line output of a command %$set% ipOutput="ipconfig" Here is the full sample, with the used macro (you don't need to undestand the macro itself) @e...

Hi , your strlen batch is wrong, you doubled S="S= SET S="S=!%~2!#" The next problem is, that your parameters are wrong when calling the batch. CALL ...\islength.bat result1 !string1! The !string1! results into the expansion to the content, but the batch file expects only a variable name, not the co...

Hi Szecska,

the cr character should be used only with delayded expansion.

So your code should be changed to

Hi,

the error is not related to setlocal, but to the call stack.
Probably you have a recursion in your code, like

Your problem is, that the spaces are outside of quotes, because of doble quoting call :info "!json!" -> call :info " {^ " a^": ^"a b c^"^, ^"b^": ^"x y z^"} " Only the red text is inside qotes, the rest is outside and the spaces are used as delimiters. You could solve that with carets in front of so...

Hi, I found a strange behaviour in the syntax error handling. I forced a syntax error with a simple %VAR:=WRONG SYNTAX% Normally you see something like "=WRONG SYNTAX% " kann syntaktisch an dieser Stelle nicht verarbeitet werden. But if the preceding line contains one of the internal-internal comman...

Hi Dave,

it's hard to remember all the problems parsing CALL/LF variables.

I retested some of the behaviour and I suppose your rules are correct now.

jeb

The question is: What do you expect?

- Simplify your test to only show the unexpected part.
- Use "set str" to show the unmodified content after the set str=... command, to be sure that the correct content is there