- Jan
- 179
- 2
Here is my test.bat showing each condition works in batch.
And here it is running in CMDebug not working.
And here it is running in CMDebug not working.
Not Defined Not Working
- Thread starter CityguyUSA
- Start date
- Jan
- 179
- 2
So I commented out the offending If statements, not something I really wanted to do because it get's confusing as to what's real code that's commented out that needs to go back in. But I wanted to try to get through this. Unfortunately, when I then breakpointed the following If structure at the top and the bottom and then ran to breakpoint it blew through both of them without stopping. Didn't see that coming. So I breakpointed every line in the if thinking maybe it was the nested one that needed the breakpoint. The rules aren't consistent. But it blew through all 10 of them.
rconn
Administrator
- May
- 14,987
- 375
Staff member
Not sure what you mean here -- BDEBUGGER is displaying "defined", which is what you got at the prompt that you said was working.
Why are you using the CMD FOR variable syntax %~1 (which means "%1 with enclosing quotes stripped") instead of just a %1?
Why are you using the CMD FOR variable syntax %~1 (which means "%1 with enclosing quotes stripped") instead of just a %1?
- Jan
- 179
- 2
See the image of CMDebug. It says it's defined. It is not there's no input. And the comparison is what really happens with out the debugger where it works correctly.
- Jan
- 179
- 2
There was nothing defined. There was nothing in the batch arguments box.
I didn't need the ~ but it didn't hurt anything either.
- Jan
- 179
- 2
I can't explain the reason the debugger came back with "defined". There was no command argument supplied. When I did it again it seemed to work correctly.