Download

BE can be downloaded from http://www.nyangau.org/be/be.zip.

Unfortunately I don't have continual access to all the platforms, so the latest improvements in one version may not yet be reflected into the others.

Installation

Installing on UNIX

  1. Copy the executable for your UNIX platform (eg: be_linux_rh90) to somewhere like /usr/bin, /usr/local/bin or ~/bin, or wherever on the path you consider appropriate, and rename it to be.
  2. Either copy the be.ini to the same directory as be so it can be found, or copy it to .berc in your home directory. BE uses your local initialisation file in preference to the common one.
  3. Optionally copy be.hlp to the same directory as be so it can be found.

On Linux, best colour and keyboard support is obtained using the regular linux or xterm terminals. On older RedHat distributions, the xterm terminfo entry may not include support for colour, and you may have to set the TERM environment variable to be xterm-color.

On AIX, best keyboard and colour support is obtained by using an aixterm, or by logging in from OS/2 using HFTTERM.EXE. It should be noted that HFTTERM.EXE appears to have a bug whereby it doesn't generate the correct datastream for the @9 and @0 keystrokes.

On SunOS, I get best keyboard and screen support when using an xterm or a vt100. SunOS xterm and vt100 terminfo entries don't include colour support. xtermc is not xterm with colour.

On HP-UX, I get best keyboard and screen support when using an xterm or a vt100.

When running aixterm or xterm its best to run with the -fg white -bg black options. This is because the Curses library and terminfo entries assume the 'original pair' corresponds to white on black.

If you use an xterm or vt100 terminal (or something that emulates them), and the system terminfo definitions for these do not include colour support, then look at the sample xterm-color.ti and vt100-color.ti files supplied with BE. These can be added to the system terminfo database by root, using the tic command (or tic_colr on HP-UX). You would use them by setting your TERM environment variable to xterm-color or vt100-color.

Installing on Windows

  1. Copy be_win.exe to be.exe, somewhere on the path.
  2. Copy be.ini to the same directory as be.exe so it can be found.
  3. Optionally copy be.hlp to the same directory as be.exe so it can be found.

BE is a Win32 application, which has had extensive testing on Windows NT, 2000, XP and 2003. Rather less testing has been performed with Windows 95, and quite a few bugs in the Windows 95 version of the Win32 Console API (used for screen redraw) have been identified and worked around. Some oddities relating to the use of the unusual screen sizes still remain. I would not be surprised if there are more problems to be found...

Note: As of Windows 2000, some newly created MS-DOS windows might have a buffer with a very large number of lines. More than the largest size BE can handle. You can change the properties of an existing Window and the shortcut that is used to start it, but there are settings inside the Windows registry covering MS-DOS windows created without a shortcut, and there is no easy GUI way to change this. We bundle console.reg, which can be run at the command line to set the default MS-DOS buffer and window sizes to 80x50.

Installing on 32 bit OS/2

  1. Copy be_os2.exe to be.exe, somewhere on the path.
  2. Copy be.ini to the same directory as be.exe so it can be found.
  3. Optionally copy be.hlp to the same directory as be.exe so it can be found.
  4. Optionally copy be.ico to the same directory as be.exe. This allows BE to have a cute icon when running in the Workplace shell.
  5. Optionally create a Workplace Shell Program Object(s) that references the BE executable. The working directory should be the directory where be.ini can be found.

Installing on 32 bit DOS

  1. Copy be_dos32.exe to be.exe, somewhere on the path.
  2. Copy be.ini to the same directory as be.exe so it can be found.
  3. Optionally copy be.hlp to the same directory as be.exe so it can be found.

Obviously, because BE for DOS is a 32 bit program, which uses a DOS extender, the machine upon which you run it must have a 32 bit processor.

Installing on NetWare

  1. Copy be.nlm to somewhere on the search path.
  2. Copy be.ini to the same directory as be.nlm.
  3. Optionally copy be.hlp to the same directory as be.nlm.

Change log

Date Changes
Various Lots of development
2014-01-16 Added support for nocode attribute on def.
Made include commands with no pattern match tagged lines, and exclude match untagged lines.
Made @Home, @End, @PgUp and @PgDn work like ^Home, ^End, ^PgUp and ^PgDn as the latter don't work on Linux.
Completely revamped the online documentation.
2014-xx-xx Added support for -Y l80.
2016-09-23 Added support for -Y noi.

Copying of this program is encouraged, as it is fully public domain. The source code is not publically available at present. Caveat Emptor.

The author of BE and this documentation is Andy Key. (email andy.z.key@googlemail.com).

{{{ Andy