Please enable JavaScript to view this site.

Take Command / TCC Help v. 28

Navigation: TCC > Commands

BDEBUGGER / IDE

Scroll Prev Top Next More
Purpose:Calls the Take Command IDE / batch debugger (IDE.EXE)

 

Format:BDEBUGGER [/C] batchfilename [/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.

 

See the IDE / Batch Debugger Operation help topic for details on the IDE menus, windows, editing, and debugging commands.

 

Options:

 

/CIf the specified batch file doesn't exist, create it without prompting.

 

/GOTOLINE:nGo to the specified line in the file after opening the tab window. For example:

 

bdebugger mytest.cmd /gotoline:24 [yourtest.cmd /gotoline:12 ...]