DosTips.com

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

I tested the behaviour described by Dave. c:\temp\with^ space.bat - WORKS \temp\with^ space.bat - FAILS with^ space.bat - FAILS But only when you try it from the command line :!: Tested in a batch file the results are different c:\temp\with^ space.bat - WORKS \temp\with^ space.bat - WORKS with^ spac...

Hi Dave, yes, in phase 2 the command token and the parameters are determined, therefore the escaping plays a role. but not for the splitting of the parameters (perhaps in pahse7 ?) It's also important for the delayed expansion phase, as this phase is executed indipendent for the command and the para...

There are two fundamental differnt ways to handle function parameters 1) Use a parameter ByValue, like you do in CALL :myFunc %str% This technic is simple but has also some limitations with special characters like quotes, spaces and carets. You should at least quote the content to presever spaces an...

This lines executes like set str1=set s1=hi cat & echo %s1% set str1=set s1=hi cat echo %s1% --- s1 doesn't contain anythig here, therefore "ECHO IS OFF" will be printed It's always a good idea to use some debugging technics (not only within batch files). View the variables, with `SET` or delayed ex...

You need to preserve the values in the ENDLOCAL-Block. @echo off set /a n=99 set ret= call :test3 ret echo show array: echo %ret.Array[0]% echo %ret.Array[1]% echo %ret.Array[2]% echo %ret.Array[3]% goto :eof :test3 setlocal EnableDelayedExpansion set /a n=0 for /L %%n in (0 1 3) DO ( set "%~1.Array...

Hi SIMMS7400, I would convert the date to julian date (number of days). Then use some math to add/subtract days and convert it back from the julian format to gregorian date. Look here :date2jdate - converts a gregorian calender date to julian day format :jdate2date - converts julian days to gregoria...

One more observation. As you already said, the scan for labels is reset at the file beginning or after a CR/LF. The label scanner reads chunks of ~512 bytes, therefore we see the described effect. BUT the scanner is able to set the new file position to the wrong position after a label is found :!: @...

Thanks Dave, your findings are impressive :D. I didn't see the idea of relative counting the characters :( I played with a file with unix style endings and a single CR/LF and thought the problem was gone as I didn't see the reset behaviour. But your analysis is really good. And your rule is really s...

Hi jfl, like Dave I'm very interessted. And I simplified your code to a minimal, failing example: @echo off goto :zwei :####################################################################################################################################################################################...

Hi jfl, nice work! Eventually I found a heuristic that seems to give good results: - If the first token is == %COMSPEC% without quotes, then this is a for /f, and I should not run AutoRun scripts. - If the second token is /c, then this a manual execution of a single command, and it's not worth runni...

Hi bosekamineni, you should use delayed expansion, because it's always safe to expand with delayed expansion. @echo off setlocal EnableDelayedExpansion set "_string=Test String With | &&<> command" echo the string is !_string! The only drawback is that you be careful with literal exclamation marks, ...