BDEBUGGER / IDE |
Purpose: | Calls the Take Command IDE / batch debugger (IDE.EXE) |
Format: | BDEBUGGER [/C] batchfilename [/Breakpoint:nn /Gotoline:nn] [parameters] |
or
IDE [/C /Gotoline:nn] file...
batchfilename |
Full name of the batch file to debug. |
parameters |
Parameters for the batch file |
file |
File(s) to edit |
File Completion Syntax:
The default filename completion syntax is: [1] dirs btm bat cmd [2*] *
Usage:
BDEBUGGER and IDE open a development environment in which files can be edited and (in the case of batch files) debugged. The difference between the two commands is that BDEBUGGER assumes that you're trying to edit & debug a batch file. BDEBUGGER will add a missing .BTM, .CMD, or .BAT extension on the filename, and it assumes that any arguments following the batch file name are batch file parameters. The IDE command is intended as a generic file editor (it supports syntax colorization for several scripting languages, including .BAT, .BTM, and .CMD batch files, Perl, Python, Ruby, and Tcl). Each argument on the command line is assumed to be a filename to be opened in a separate tab window. IDE also does not process any variables, quotes, escape characters, or redirection on the command line.
The IDE editor will display document changes in the margin and in the text. In the text, inserted characters appear with colored underlines and points where characters were deleted are shown with small triangles. The margin shows a block indicating the overall state of the line. The states are modified (orange), saved (green), saved then reverted to modified (green-yellow), and saved then reverted to original (cyan). The change history can be toggled on or off with the "Options / Change History" menu entry.
The IDE editor allows you to create and edit NTFS streams. The syntax is "filename.ext:streamname".
See the IDE / Batch Debugger Operation help topic for details on the IDE menus, windows, editing, and debugging commands.
Options:
bdebugger mytest.cmd /gotoline:24 [yourtest.cmd /gotoline:12 ...]