


















nothing


















bx_case"bx_case,bx_hop,bx_jump,bx_switch"

bx_case inserts a "case" statement at the cursor position and leaves
the cursor on the colon:

    case :
    {

      break;
    }

Once you have typed the case value, you can use bx_hop to place the
cursor just above the "b" of "break". 

After typing the case statement, you can use bx_jump to place the
cursor just after the closing curly bracket "}". 



bx_comment"bx_comment"

bx_comment inserts /* */ at the cursor position and leaves the cursor
between the comment delimiters.















bx_count"bx_count"

bx_count counts the number of occurrences of a pattern in the current
buffer. The current regular expressions and case sensitivity settings
are used by bx_count.

The pattern can be typed in the command line. The command shown below,
for instance, counts the number of occurrences of the string "abcd": 

      bx_count abcd

In the next example, bx_count counts the number of lines with trailing 
blanks. The pattern is a regular expression and must be enclosed between
quotes:

      bx_count "[ ]+>"


                                                   PgDn ==> Next page

If no pattern is specified in the command line, bx_count tries to "guess"
what the pattern is as follows:

If a part of a line is marked, the text marked is taken as the pattern.
Otherwise, if the cursor is positioned on an alphanumeric string, that
string is assumed to be the pattern.

In either case, the pattern selected is shown in the command line where
you can edit it before pressing Enter.







PgUp ==> Previous page
bx_curl_brkts"bx_curl_brkts"

bx_curl_brkts inserts a matching pair of curly brackets at the cursor
position and leaves the cursor between the brackets as shown below.  The
exact position of the cursor depends on your current tab settings.

  {
     
  }


When you have finished typing between the brackets, you can use bx_jump
to place the cursor just after the closing bracket "}". 






bx_date"bx_date"

bx_date   inserts today's date at the cursor position.  
















bx_del"bx_del"

bx_del deletes the current file (this is the file which is in the current
window).  bx_del asks you to confirm that you want to delete the file
and if you answer Y or y, it deletes the file from your disc.

The request is rejected if the file is the only one currently open.












bx_do"bx_do,bx_mac"

bx_do enables you to run commands inside Brief. The command output is
redirected to a file.  When the command is complete, the output file
is automatically edited so that you can examine the result.

The error output which is normally sent to stderr can also be redirected
to the output file.

The default output file is "DO.TMP". It is created in the directory
specified by the XTEMP configuration parameter or in the current
directory if XTEMP is undefined.

With bx_do, you can either enter a command from the keyboard or you
can select a command or macro from a file which you have previously
set up. 

                                                   PgDn ==> Next page


To enter a command from the keyboard
------------------------------------
Press the bx_do key and type the command in response to the "DO:"
prompt.  

For instance, if you type

   DIR /B /AA *.c
   
you obtain a list of all the C files in the current directory which
have the Archive bit set.  




PgUp ==> Previous page                             PgDn ==> Next page


To select a command or macro in a list
--------------------------------------

If you press only the ENTER key in response to the "DO:" prompt, bx_do
displays the contents of the command file in a menu.  You can then
select the command or macro you wish to execute.  Alternatively, you can
press Alt-e to edit the list of commands.

The command file is a text file whose full path is given by the
XCMD configuration parameter. By default, the file name is ".\cmd.bx".

The format of the command file is explained further down.



PgUp ==> Previous page                             PgDn ==> Next page


To select a macro in a list
---------------------------

If you press the bx_do key twice in succession, the bx_mac macro is
invoked. This feature obviates the need to assign a separate key to
bx_mac.  

The use of bx_mac is documented in another help section.







PgUp ==> Previous page                             PgDn ==> Next page


The command file
----------------

A list of frequently used commands can be stored in a text file which
you prepare with Brief.  

There must be only one command per line. Empty lines are ignored.
Leading white spaces are discarded.  Comments prefixed by "//" are
allowed.

A command can have one or more parameters. Parameters must be separated
by spaces.



PgUp ==> Previous page                             PgDn ==> Next page


The standard output is always redirected to a file. If you do not
specify an output file, bx_do directs the output to "DO.TMP" in the
directory specified by XTEMP.  Examples:

   DIR *.c                 // output file is default ("do.tmp")
   DIR *.c >dir.tmp        // output file is "dir.tmp"
   DIR *.c >>dir.tmp       // output is appended to "dir.tmp"

The error output can also be redirected to the output file. If you do
not specify an output file, the error output is redirected to "DO.TMP". 
To redirect the error output to the output file, you must put an
ampersand "&" between the redirection indicator ">" and the file name.

Examples are shown on the next page.

PgUp ==> Previous page                             PgDn ==> Next page


   DIR *.c                 // output file is default ("do.tmp")
   DIR *.c >&dir.tmp       // output file is "dir.tmp"
   DIR *.c >>&dir.tmp      // output is appended to "dir.tmp"

When the error output is not re-directed to the output file, Brief
clears the screen before running the command.

The standard input can also be re-directed. Example:

   SORT <%F >&newfile      // Sort current file (%F is explained below)

Please refer to the dos() macro in the Brief Macro Language Guide for
further information.


PgUp ==> Previous page                             PgDn ==> Next page


Before a command is executed, some text replacement can take place.
This feature is controlled by the five symbols %D, %E, %F, %N, %M.

   %D is replaced with the name of the CURRENT WORKING DIRECTORY

   %F is replaced with the FULL NAME of the current file. E.g.:
      "\dir1\dir2\myfile.txt"
      (The current file is the file in the current window).

   %E is replaced with the EXTENSION part of the current file name.

   %N is replaced with the NAME of the current file, without the
      extension part or path.


PgUp ==> Previous page                             PgDn ==> Next page

   %M is replaced with the portion of text which is MARKED on your 
      screen. If the area marked exceeds a single line, it is ignored
      and %M is deleted from the command. The same happens if no text
      is marked.

Further examples of valid commands:

%M                           // Execute command marked on screen
DIR /ON /AA /B *.c           // List amended C files in bare format
                             // (files can be edited with bx_open)
SORT <%F >&newfile           // Sort current file --> newfile
GREP -i+ %M \dir1\dir2\*.h   // Run GREP with pattern marked on screen 
LINT -zero -b std.lnt %F >&lint.log     // Run LINT on current file
\DOS\FC /L /W %F \brief\backup\%N.%E    // compare current file with 
                                        // previous copy

PgUp ==> Previous page                             PgDn ==> Next page


Finally, you can also include macros in the command list. Each macro
name must be preceded by the keyword "MAC " e.g. "MAC toupper". The text
replacement symbols "%M" etc. can be used in macro calls. Examples:

MAC bx_ffile %M            // Find file whose name is marked on screen
MAC bx_grep                // Execute bx_grep. Macro will prompt
MAC bx_grep "abcd *.c"     // Execute macro bx_grep 
MAC bx_grep "%M"           // %M must be replaced by full option line 
MAC tabs 5 14 21 30 33     // Set tabs
MAC %M                     // Execute macro marked on screen

NOTE: in bx_grep "%M" above, the quotes are necessary to ensure that the
macro is called with a single parameter e.g. "-i+ abcdef \dir1\dir2\*.h"


PgUp ==> Previous page

bx_viewhex"bx_viewhex"

bx_viewhex displays a file in hexadecimal. The hexadecimal display is
placed in a file called "HEX.TMP" and this file is automatically
opened for viewing.














bx_mac"bx_mac,bx_do"

When invoked, bx_mac displays a list of macros in a selection menu and
lets you chose the macro to be executed.  

The list of macros is held in a text file which you can prepare with
Brief.  The name of any macro can be entered in this file.
For instance your file could look like this:

   toupper
   use_tab_char  y    // fill empty areas with tab characters
   use_tab_char  n    // fill empty areas with spaces
   tabs 10 20 30 
   edit_file \dir1\dir2\dir3\dir4\myfile
   bx_viewhex         // view a file in hexadecimal
   bx_funlist         // make list of functions in current file
   bx_grep            // execute GREP inside Brief

                                                    PgDn ==> Next page

Blank lines and leading white spaces are ignored. Comments, prefixed by
"//", are discarded.  Macros can have parameters.

When the macro selection menu is displayed, you can press Alt-e if
you wish to edit the list of macros.

If bx_do is assigned to a key, you do not need to assign another 
key to bx_mac because bx_mac is executed if you press the bx_do key
twice in succession.


The full path of the macro list file is given by the configuration
parameter XMAC.

By default, XMAC is set to ".\macros.bx".

PgUp ==> Previous page
bx_ffile"bx_ffile"
bx_ffile performs a file search.  It can search all the directories or
just a branch. Wildcard characters "*" and "?" can be used to specify
the files to look for.

The files found are shown in a menu from which any number of files can
be selected for editing. Alternatively, you can press Alt-e to place the
list of file names in a text file which you can then edit.

bx_ffile does not find hidden files or files in hidden directories.

When activated, bx_ffile asks you to enter a file specification such as:

   *.h         to search the current directory and its sub-directories
   \*.h        to search all the directories
   \dira\*.h   to search "dira" and its sub-directories

You can also mark the file specification on the screen before invoking
bx_ffile.
bx_index"bx_index"

bx_index searches the current buffer for lines starting with a 
particular pattern.  The lines found are displayed in a selection menu.
From this menu, you can select the line where you want to place the
cursor. If no matches are found, the pattern is displayed in the
status line so that you can check it.

The pattern can be specified by the configuration parameter XIKEY. It
can also be specified by the keyword BX_INDEX_KEY placed in the file
itself. The pattern specified with BX_INDEX_KEY has precedence over
that defined with XIKEY.

The pattern is always treated as a regular expression. 

The search always starts in column 1 of each line, i.e. the character
"<" is automatically prepended to the pattern.

                                                    PgDn ==> Next page

By default, the search is performed with case sensitivity on.  You can
change that if you use BX_INDEX_KEY.

BX_INDEX_KEY should be placed near the top of the file.

The syntax is:    BX_INDEX_KEY = pattern  [case] [DEBUG]

There can be any number of white spaces before and after "=".

   pattern  can include embedded white spaces.
            
   case     is optional. It can be CASE_ON or CASE_OFF.

   DEBUG    is optional. When DEBUG is specified, the key is displayed
            in the bottom line and no menu is displayed.

PgUp ==> Previous page                             PgDn ==> Next page

Examples:

  BX_INDEX_KEY=[0-9].  

      Will find lines starting with a number followed by a dot.

  /* BX_INDEX_KEY = {struct}|{union}
  */
      Will find lines starting with "struct" or "union".

  BX_INDEX_KEY = {  }[A-Z]{ }\t
   
      Will find lines starting with two spaces followed by an upper
      case letter, another space and a TAB.


PgUp ==> Previous page
bx_fbb"bx_fbb,bx_fbf"

bx_fbb searches backwards for the left curly bracket "{" which matches
the right curly bracket "}" currently under the cursor. 

bx_fbb assumes that the current buffer contains a C source file.
Starting from the beginning of the file, it performs a syntax analysis
in order to find the matching "{".  While doing so, it skips any curly
brackets which are present in comments (e.g. /* } */), or between single
or double quotes. 

The search may become slow if the construct "{....}" is far down the
file.

A fast but less rigorous version of this macro is also available.




bx_fbf"bx_fbf,bx_fbb"

bx_fbf looks forwards for the right curly bracket "}" which matches the
left curly bracket "{" currently under the cursor. 

bx_fbf assumes that the current buffer contains a C source file. It
performs a syntax analysis in order to skip any curly brackets which are
present in comments (e.g. /* } */), or between single or double quotes. 

The search may become slow if the closing "}" is far from the opening "{".

A fast but less rigorous version of this macro is also available.







bx_for"bx_for,bx_hop"

bx_for inserts a "for" statement at the cursor position and leaves
the cursor between the parentheses:


    for(  )
    {
      1
    }


You can use bx_hop to place the cursor in position 1.






bx_ffun"bx_ffun"

bx_ffun looks for a C (or CB) function definition and places the cursor
on it.  bx_ffun first searches the current file (the file in the current
window).  If the function is not in the current file, bx_ffun can also
search other files if you have previously set up a function index. This
is explained in detail later.

Like the Brief "routines" macro, bx_ffun can only find function
definitions which start in column 1 and occupy a single line terminated
by ")". Whitespaces after the ")" are ignored.

When bx_ffun is invoked, it checks whether the character currently under
the cursor is a letter, a digit or the underscore "_".  These are the
only characters allowed in a C function name and we refer to them here
as "F-chars". 

                                                   PgDn ==> Next page


If the character under the cursor is an "F-char", bx_ffun assumes that
the text string under the cursor is the name of the function you are
looking for.  The function name is delimited at each end by any non
"F-char".  

If on the other hand, the cursor is not positioned on an "F-char",
bx_ffun asks you to type the name of the function you are looking
for.

As mentioned above, you can set up a function index to tell bx_ffun
which files to search when you look for a C function.  The index is
held in a text file which can be prepared with Brief. This is explained
with a few examples below.


PgUp ==> Previous page                              PgDn ==> Next page


Suppose that you are working on a package which consists of four source
files: "init.c", "main.c", "ios.c" and "stop.c".
Suppose also that you have adopted a systematic naming scheme for your
functions such that, for instance, all functions in file "init.c" are
called "in_...", all those in "main.c" are called "ma_...."  etc. 

In this case, the function index is easy to set up. It should contain:

in_   init.c
ma_   main.c
io_   ios.c
st_   stop.c

For any function starting with "in_", bx_ffun will search file "init.c".

PgUp ==> Previous page                              PgDn ==> Next page

Suppose now that some functions in "init.c" are called "INI_..." and
that "main.c" is replaced by "main1.c", "main2.c" and "main3.c".  The
function index should be amended as follows:

in_   init.c
INI_ 
ma_   main1.c
+     main2.c
+     main3.c
io_   ios.c
st_   stop.c

The first two lines tell bx_ffun that it should search "init.c" for
any function with the prefix "in_" or "INI_". 
Lines 3 - 5 specify that "main1.c", "main2." and "main3.c" should be
searched for any function name starting with "ma_".

PgUp ==> Previous page                              PgDn ==> Next page

Suppose, finally, that you have two more files "\dir1\misc1.c" and 
"misc2.c" in which the function names do not follow any rule.  This
can also be accommodated. You simply need to add two lines to the
index:

*     \dir1\misc1.c 
+     misc2.c 
                                             
These lines mean that bx_ffun should search "misc1.c" and "misc2.c"
for any function name not found in the other files.

The "*" matches any function name.



PgUp ==> Previous page                              PgDn ==> Next page

In the worst case, the index would look something like this:

*    file1
+    file2
+    file3
etc.


Note that the following index is valid but inefficient since file
"file1.c" will always be searched before the other files.

*       file1.c
abc     file2.c     (search file2.c if function name is abc....)
def     file3.c


PgUp ==> Previous page                              PgDn ==> Next page

The layout of the index file must respect the following rules:

An index line can have one or more fields. Fields are separated by
white spaces (a white space is a space or tab character).
The length of an index line is limited by the maximum line length
configured in Brief.

The first field is always a function name prefix, or the character "+"
or "*".  It must start in column 1. (If the character in column 1 is
NOT a letter, an underscore "_", an asterisk "*" or a plus "+", the
line is ignored).

A name prefix will match any function name starting with this prefix.
The character "*" matches any function name.  The character "+"
always stands for the last prefix or "*" encountered.

PgUp ==> Previous page                              PgDn ==> Next page


The second field, when present, is always a file name.  This can be a
full pathname or a path relative to the current directory. 

When no file name is specified, the last file name encountered is used
by bx_ffun.

Any text found after the second field is ignored. 



The full path of the index file is given by the BX configuration
parameter XCINDX whose default value is ".\cindex.bx".



PgUp ==> Previous page

bx_funhdr"bx_funhdr,undo"

bx_funhdr places the cursor on the first line of the C or CB function
within which the cursor is currently positioned. This enables you to
see easily where you are in your source file.

You can use Undo to return the cursor to its original position.












bx_funlist"bx_funlist"

bx_funlist makes a list of all the function definitions found in the
current buffer.  The list is placed in a file called "FUNLIST.TMP" which
is automatically opened for editing. This file is created in the
directory specified by the configuration parameter XTEMP or, if XTEMP is
undefined, in the current directory.

bx_funlist assumes that the current buffer contains a C or CB source file.

Like the Brief "routines" macro, bx_funlist can only find function
definitions which start in column 1 and occupy a single line terminated
by ")". Whitespaces after the ")" are ignored.






bx_grep"bx_grep"

bx_grep  enables you to run GREP inside Brief. GREP.EXE must be in
the current path. 

In general, the output produced by GREP is placed in a file called
"GREP.TMP".  This file is automatically opened so that you can look
at it without leaving Brief.

Depending on the switches used, GREP may display file names only.
In this case, the list of files produced by GREP can be shown in a
a selection menu from which you can pick any number of files for
editing.

A selection menu is used only if the BX configuration parameter
XGREPMENU is set to "yes" (see also -M+ below). 

                                                    PgDn ==> Next page


When invoked, bx_grep displays a prompt such as "GREP (RE on):" to
invite you to type a search command. You can then type any valid GREP
command, for instance:  -i+ abc[0-9] *.c *.h

Note that the prompt tells you whether Brief regular expressions are 
currently enabled or not. If they are and if you do not want GREP to
treat your search pattern as a regular expression, you must include the
switch -r- in your command.  Conversely, if Brief regular expressions 
are disabled, you may need to include -r+ in your command.

Sometimes you may wish to override the effect of XGREPMENU. You can
do this by including the switch -M- or -M+ in front of your GREP
command.  -M- means do not use a selection menu.


PgUp ==> Previous page                              PgDn ==> Next page


When the use of a selection menu is enabled, you never need to include
the switch -l+ in your GREP command.  bx_grep adds -l+ to your command
when this is not incompatible with your other switches.

Before invoking bx_grep, you can mark a portion of a line on your
screen to indicate the text you want GREP to look for.  This text is
automatically inserted in the GREP command where you can edit it if
necessary.

To see the GREP help summary, simply type "?" after the prompt.  The
summary is shown in a file called "GREP.TMP" which you must close 
before invoking bx_grep again.

For more information, press Alt-h when the file selection menu is
displayed.

PgUp ==> Previous page
bx_gr"bx_gr"
bx_gr performs global replacements in selected files.

You specify the pattern you want to replace and the replacement string.
You also specify whether the pattern is a regular expression and whether
pattern matching must be case sensitive.

Global replacements are performed in three steps as explained below.

First bx_gr makes a list of all the files which contain the pattern
you want to replace.  

Next, the list of files found is presented to you in a selection menu.
You can then tag the files you actually want to amend.

Once you have tagged the files to be amended, you press a key to
initiate the third step in which the global replacements are performed. 

You can press ESC at any time to abort the operation.
bx_gs"bx_gs"

bx_gs provides a facility similar to GREP: it enables you to search a
group of files for a pattern. 

bx_gs first displays a dialogue box in which you can enter your search
details. The search pattern can be a Brief regular expression.

Before invoking bx_gs, you can mark a portion of a line on your screen
to indicate the text you want to look for.  This text is automatically
inserted in the pattern input field of the dialogue box.

After completing a search, bx_gs displays a menu showing the names of
the files which have at least one instance of the pattern.
From this menu, you can select one or more files to edit. Alternatively,
you can press Alt-e to save the list of file names in a text file.

For more information, press Alt-h when the dialogue box or file selection
menu is displayed.
bx_hop"bx_hop"

bx_hop places the cursor between the next pair of curly brackets. 

For instance, if the cursor is in position 1 when you invoke bx_hop, the
cursor moves to position 2.  Next time it moves to position 3.


    if( 1 )
    {
       2
    }
    else
    {
       3
    }



bx_if"bx_if,bx_ifelse,bx_hop,bx_jump"

bx_if inserts an "if" statement at the cursor position and leaves
the cursor between the parentheses:


    if(  )
    {
      1
    }


You can use bx_hop to place the cursor in position 1.

When you have finished typing your code in the "if" body, you
can use bx_jump to place the cursor just after the closing "}". 



bx_ifelse"bx_ifelse,bx_if,bx_hop,bx_jump"

bx_ifelse inserts an "if-the-else" statement at the cursor position
and leaves the cursor between the parentheses:

    if(  )
    {
      1
    }
    else
    {
      2
    }

You can use bx_hop to place the cursor in position 1 and then 2.




bx_jump"bx_jump"

bx_jump places the cursor just after the next bracket "}":
















bx_keys"bx_keys"

bx_keys  enables you to assign BX macros to keys.
















bx_licence"bx_licence"

bx_licence  will save your BX licence number in file LICENCE.BX.

If file LICENCE.BX is accidentally damaged or lost, you can recreate it
as long as you keep a copy of your licence number.

To recreate LICENCE.BX:

   1) delete LICENCE.BX (assuming it still exists)

   2) Start Brief and, when prompted, re-enter your BX registration
      details. Your name and company name must be typed exactly as
      you originally typed them.

   3) Execute macro bx_licence. You will be prompted to key-in your
      licence number.


bx_lpt"bx_lpt"

bx_lpt lets you select the printer port Brief will use when you invoke
the print command.  The printer port can be LPT1 or LPT2.

Any selection you make with this macro does not affect the printer port
selected with the DOS 'print' command.

By default, Brief uses LPT1.  You can change this to LPT2 by including
the line "XLPT = LPT2" in your BX configuration file or by adding the
command "set XLPT = LPT2" in your AUTOEXEC.BAT file.

When bx_lpt is called from the keyboard, the printer port can be
specified in the command line, e.g.:

     bx_lpt LPT2



bx_notes"bx_notes"

bx_notes enables you to edit a notes file at any time without losing
your position in the current buffer. 

The full path of your notes file is given by the XPAD configuration
parameter. For instance:

   set XPAD=\dir1\notes.txt

By default, XPAD is set to ".\notes.txt"

bx_notes is most effective when assigned to a key.  When you press
that key, bx_notes takes you immediately to your notes file. You can
then work on the file in the usual way. When you press the notes-key
again, bx_notes takes you back to your original buffer. You can also
close the notes file or edit another file in the usual way.

                                                    PgDn ==> Next page

bx_notes can be used in conjunction with bx_index. This is useful if 
your notes file is organised in sections with headings. 

bx_index is invoked automatically each time you go to your notes file
if you assign the value bx_index to the XPMAC configuration parameter
e.g.: 

      set XPMAC=bx_index

(If you prefer, you can use another macro instead of bx_index.)






PgUp ==> Previous page
bx_open"bx_open"

bx_open causes Brief to edit the file identified by the text under the
cursor or marked.  Only files which exist can be edited in this way.

A file can be specified by a relative path (cases 1 and 2 below) or
by a full path (case 3):

      1) myfile.txt
      2) subdir1\myfile.txt
      3) \mydir\subdir1\myfile.txt

When a file specified by a relative path cannot be found, "bx_open"
also tries the paths specified by the XOPATH1 and XOPATH2
configuration parameters.

In case 3, bx_open only tries the full path specified.

                                                   PgDn ==> Next page

Unless the file identifier is marked, it must be delimited. 

A file identifier can be delimited at each end by any character which
is not allowed in a file name:  tab space * + = [ ] ; | < > ? 

The file identifier can also be delimited on the left by BOL and on the
right by EOL or  ":".

In addition, if the cursor is on a left parenthesis, "(" and ")" are
then treated as delimiters. In case 1 below, bx_open attempts to edit
"myfile" while in case 2 it will edit "(myfile)".

       case 1    (myfile)               case 2   (myfile)
                 ^                                 ^


PgUp ==> Previous page
bx_pntr"bx_pntr"

bx_pntr inserts "->" at the cursor position and leaves the cursor on
the right of the ">":

    ->













bx_sort"bx_sort"

bx_sort enables you to run the DOS SORT program inside Brief.

You type the SORT parameters in a dialogue box.  These are the file to
be sorted, the sorted file, the column number and the sort order.













bx_srchb"bx_srchb,bx_srchf"
bx_srchb initiates a search backwards for the text which is currently
under the cursor or which is marked. Regular expressions are turned off.

If no text is marked, the following rules apply:

The text string can contain letters, digits, underlines "_" and
dots ".".  Other characters are treated as delimiters.

The dot has a special function: it is treated as a delimiter except
when the cursor is positioned on it.

For instance, if you invoke bx_srchb while the cursor is positioned
as shown below, a search for "user_id" is initiated.  However, if the
cursor is on the dot, a search for "user_id.name" is initiated.

                        user_id.name
                             ^
After using bx_srchb, you can use the Brief "search_again" macro.
bx_srchf"bx_srchf,bx_srchb"

bx_srchf  is similar to bx_srchb but initiates a forward search.
















bx_switch"bx_switch,bx_hop,bx_case"

bx_switch inserts a switch statement at the current cursor position and
leaves the cursor between the parentheses:

    switch( )
    {
      1
    }

You can use bx_hop to place the cursor in position 1 and then bx_case to
insert a case statement. 

Please refer to bx_case for more information.





bx_vkeys"bx_vkeys"

bx_vkeys  enables you to produce various lists showing the current key
assignments.  

In particular, you can list all the keys currently unassigned, the keys
assigned to the BX macros, those assigned to non-BX macros etc.

Each list is saved in a file of your choice. 










bx_while"bx_while,bx_hop"

bx_while inserts a "while" statement at the cursor position and leaves
the cursor between the parentheses:


    while(  )
    {
      1
    }


You can use bx_hop to place the cursor in position 1.






Overview

Please see User Manual (MANUAL.TXT)

