home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Stars of Shareware: Windows Spiele
/
SOS-WIN_SPIELE.ISO
/
best_50
/
bedit14.zip
/
READ.ME_
/
READ.bin
Wrap
Text File
|
1994-03-17
|
14KB
|
248 lines
Bedit read.me file
This file briefly describes the features of version 1.4 of the Bedit
editor and how to setup and use it. Input from enthusiastic users
has been invaluable in choosing features for the Bedit editor. A few
users also found bugs that we had not seen. These have mostly been fixed
in version 1.4. Since we have continued to test Bedit, we have found
and fixed other bugs as well.
Before describing the features of V1.4, we wish to explain what is
happening with the Bedit editor. V1.4 is the last version of Bedit to
be available for shareware registration. We have developed V2.0.
Since almost all of our sales have been of Professional Bedit,
V2.0 will only be available as the Professional version.
All levels of the Bedit editor feature:
1) Unlimited file size (limited by virtual memory)
2) Keyboard and mouse configurability with default vi emulation
3) Windows standards maintained
4) Windows MDI used to allow editing of almost unlimited number of files
5) files may be dragged/dropped into Bedit
6) text copy/move with the mouse
7) Finding text can be done with the middle mouse button.
8) Bedit V1.4 provides simple (limited) ex command line emulation.
9) Macros are recorded and editable. They can be executed a single
time or iterated within a line range. The line range can be
specified with any combination of line numbers and marks.
10) Macros may be played "silently", not showing changes until the
iteration is completed. This speeds up execution by at least
a factor of 10! A check box has been added to the macro iteration
dialog box to specify whether or not to "Watch changes" during
the iteration. (The initial condition of the check box is
configurable.)
11) Macro iteration, and search/replace all are interuptable.
This gives more security.
12) The meaning of the buttons on the button bar are shown on the
status bar when the mouse is over the buttons.
13) The file Re-read Operator provides a simple interface with other
programs concurrently updating files while editing. (E.g.
spelling checkers and resource tools.)
14) Insert File, copies, pastes, deletes, etc. are not size limited
(within machine capacities).
15) Buffer size is configurable. A small buffer size results in
faster text entry while larger buffers provide better display
and scrolling. A buffer size of 5KB is recommended for slower
machines such as a 386 while 10KB is recommended for faster
machines.
16) The status bar displays lots of information, including: current
line and column, current char in hex, editor states, file size,
and a modified indicator.
17) A user manual is available that includes examples and tables not
found in the on-line help.
18) The default font is user selectable when changing the
screen font of a file.
Version 1.4 has several new features. See the manual or on-line help
for details.
1) An Operator was added to emulate the vi undo/redo toggle. This
Operator will probably be of little interest since the standard
Undo and Redo Operators are more powerful.
2) Paste Before and Paste After Operators were added to emulate the
vi P and p functions more accurately. The original Paste Operator
is still available to maintain Windows consistency.
3) MANY changes were made for V1.4 to improve the detailed consistency
between the Bedit Operators and corresponding vi functions.
Windows standards were maintained for the "gray" keys while the
Operators act like vi functions.
4) The command mode caret is now an underscore.
5) The Bedit sounds can be turned off using the Options menu item
"Play Sounds".
6) The Windows/Tile menu item allows either horizontal or vertical tiling.
7) Operators were added to emulate the vi t, T, and 0 functions. These
are the Find to Char, Find to Char Back, and GoTo Column1.
(On-line help only)
V1.4 has several bug fixes as compared to V1.3. In V1.3 the following bugs
existed:
1) The default font was ignored if Bedit was opened with
BringUpWithFiles = FALSE, or if brought up with file parameters.
2) While editing macros, it was not possible to delete char combinations
3) If your PATH has the Bedit directory after character 1024, the
configuration and help files cannot be found in the PATH.
4) Sometimes when a macro was assigned to a Ctrl or Shift key combination
the editor was left thinking that the Ctrl of Shift key was still
held down after the macro was executed.
5) plus more bugs fixed
Version 1.4 requires approximately 1.2 MB of disk space.
The following additional features are available in Bedit V2.0 (which is
Professional only):
1) A new edit control that is faster, smoother, lacks some bugs that
exist in the edit control used in Bedit V1.x.
2) Command Line Operator line numbering as in :set number
3) User selectable coloring for the text and background of edit windows.
4) Selective write from the Command Line (as in :4,8w)
5) Show unseen chars as in :set list (also from Options/Show Unseen Chars)
- there is a setup option under Options/Show Unseen Setup
to select the chars to show in place of the unseen chars
6) Macros can be marked to allow the Repeat Change Operator to
execute them
7) Macros can be imported from any saved macro file (copied from
bedit.mac typically found in the Windows directory)
8) Macros can be copied or renamed from the Commands/Macro Maintenance
dialog.
9) Multiple edit windows can be used with one file
- Changes made in any window are reflected in another when
that one becomes active
10) Other Windows or DOS programs can be executed from Bedit:
- The Command Line Operator can be used to start a Windows
program if no line range is specified (as in :!msoffice)
- A DOS program can be executed with or without a line range.
If no line range is specified, a DOS window is created and the
DOS program is started in it. If a line range is given, those
lines of the file are piped through the DOS program and the
output replaces those lines in the file.
- There is a new Pipe Operator that pipes specified lines through
the given DOS program like :!. This Operator allows a motion,
including going to mark points, as well as repetition of the
Operator to specify the line range. The Pipe Operator also works
with the new Block mode to pipe columns of text through a DOS
program.
11) The number of history lines for the Command Line Operator was
increased from 20 to 50.
12) Command line "set" or "set all" (i.e. :set) to show all settings
13) Ctags functionality.
14) Number registers for deleted strings (as in "1)
15) Line numbering is saved/restored with other file info
16) Operators for vi's t and T (Find to Char and Back).
17) Optional vi syntax for find regular expressions: see Options Menu
18) Block off the status bar to make it less mobile and easier to
spot changes in specific fields (also more efficient)
19) Column selection with cut, paste, pipe, etc. For example, you may
want to move columns 20-35 of lines 93-112 after column 5 either in
the same lines or in other lines. This involves a new Toggle Block
Selection Operator. The Pipe Operator also operates on blocks of
text if in block mode.
20) "Named macros" in the sense that the name of a macro can be entered
in the text and the Substitute Macro Operator can be used to clear
the name and execute the macro. The simplest form of this gives
you abbreviations, and also text templates.
21) Enter Command String Operator to provide macro interface for the
Command Line functions.
22) Go To Column 1 Operator for vi "0" function.
23) Search/replace dialog can be configured to go away after it is used.
24) Placement of search/replace dialog is setable from Commands Menu
when the dialog is up.
25) Direction of repeat searches can be configured to be inconsistent
like vi.
26) Keyboard delay and repeat rates are configurable
27) The size of the font of the status line is configurable.
28) Insert Over Operator for the vi "R" function.
29) The directory for the backup files can be configured.
30) Find String Up Operator for vi "?" function.
31) DefaultExt parameter in the configuration file now works.
32) Optional network installation
33) Longer lines (up to about 10% less than configured buffer size),
potentially as long as 13K characters in a line.
34) Longer search strings (up to line size).
35) Macro editing allows an escape character to be placed in a macro.
To register Bedit V1.4, you can call J & B Star Software at a number given
below and provide a credit card number for Visa, Master Card, or American
Express. The charge is $35. If a manual and diskette are required, they
are an additional $15 if mailed to a continental US location (US mail).
State sales tax of 3% applies to all sales to Colorado residents.
Bedit V2.0 is available at an introductory price of $99 until 5/1/94. Since
V2.0 has so many new features plus improved packaging and manual, the price
of V2.0 beginning 5/1/94 will be $120, including continental US ground
shipping. Other arrangements will cost more. State sales tax of 3%
applies to all sales to Colorado residents. Call (800) 484-9490
(with security code 7841) or call (303) 660-1796. You can pay by Visa,
MasterCard, or American Express. Purchase orders are accepted from
businesses. You can also send a check or money order to:
J & B Star Software
P.O.Box 878
Castle Rock, CO 80104
Bedit Editor Installation From Windows 3.1:
Run the setup.exe from the Bedit Editor installation files (using
the Windows Run command) and follow the instructions.
NOTE: Bedit will not work in Windows 3.0.
Configuration File:
The Bedit editor is a highly configurable editor. The Bedit editor
can be made to function similar to some other Windows or UNIX
editors (such as vi(TM of AT&T)) or as a completely custom editor.
Two sample configuration files are included with the Bedit editor.
They are beditcfg.win and beditcfg.unx. One is typical of other
Windows editors while the other provides an enhanced vi emulation.
In keeping with its configurability, Bedit will not run without
a configuration file. The configuration file for Bedit is called
bedit.cfg and is a text file. The default configuration file is a
copy of beditcfg.unx. The Bedit setup procedure creates a Program
Manager group that includes an item to edit the Bedit configuration
(bedit.cfg) using the Bedit editor. The Bedit configuration file is
normally kept in the same directory as the Bedit editor (bedit.exe).
However, bedit.cfg may be placed in any other directory if an
environment variable is set for it. See below for details.
Using the Bedit Editor:
After installing Bedit, full on-line help is available by running
the Bedit Program Manager item for Bedit.hlp, or running Bedit.exe
and selecting the question mark button or pressing F1. We think you
will find the Bedit editor to be as simple or as complex as you need
it to be.
Optional Environment Variables:
Some advanced users may wish to place the Bedit.cfg or Bedit.hlp files
in a different directory than Bedit.exe. Environment variables can be
set to provide the paths for those files if they are not to be in the
PATH. These variables are BEDITCFG and BEDITHLP. Do not include the
file names in the path given in these variables. The file names are
always Bedit.cfg and Bedit.hlp.
Bedit Use and Registration:
If you have purchased a copy of the Bedit editor, please call (800) 484-9490
(with security code 7841) if you have any questions, comments, or
suggestions. We can be reached on CompuServe at user ID 72640,3347 and
on America Online at user ID "Bedit". An unregistered copy of Bedit can be
found on shareware Bulletin Boards. An unregistered copy of Bedit can be
converted to a registered copy using a "key" that can be obtained from
J & B Star Software over the phone. Please distribute the unregistered
Bedit software or demo version to anyone who may be interested in a high
quality, powerful, and configurable text editor for Windows 3.1+. It is
illegal to distribute a registered copy of the Bedit software. It is
illegal to use an unregistered copy of Bedit for more than 30 days. It is
legal to use a registered copy of the Bedit editor only on one
PC at a time. Reduced rates are available for high volume purchases.
Trademarks
Windows, Windows NT, and WorkGroup for Windows are registered trademarks
of Microsoft Corporation. Ex and vi are trademarks of AT&T. UNIX is a
registered trademark of USL. DeskEdit is a registered trademark of
Symantec, Inc. The Bedit editor is copyrighted 1993 to J & B Star
Software. All rights reserved.
Disclaimer and Agreement: Users of the Bedit editor must accept this
disclaimer of warranty: The Bedit editor is supplied as is. The author
and J & B Star Software disclaim all warranties, expressed or implied,
including, without limitation, the warranties of merchantability and of
fitness for any purpose. The author and J & B Star Software assume no
liability for damages, direct or consequential, which may result from
the use of the Bedit editor.