home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
OS2
/
CEDIT11.ZIP
/
CEDIT.DOC
next >
Wrap
Text File
|
1994-03-09
|
6KB
|
158 lines
CEDIT 1.1 DOCUMENTATION
Copyright (C) 1994 by J. Frijters
March 13, 1994
CEDIT 1.1 DOCUMENTATION PAGE 1
Introduction
CEDIT is an almost-Norton-Editor-compatible text editor for OS/2 2.x. Its
purpose is not to be 100% compatible, but to closely emulate NE and
deviate from it only where the author felt it necessary.
CEDIT is a freeware program; this means that your are allowed to
distribute and use this program and its documentation, provided it is
unmodified, without paying.
If you choose to use this program, you agree that the author and his
company cannot and will not be held responsible for any damages arising
from the use or misuse of the program or its associated documentation.
Features
This section is a highlight of some features that CEDIT provides:
- Norton Editor compatible
- 32 bit OS/2 2.x application
- Long filename and extended attribute support
- Edits files up to 50Mb
- Unlimited line length
- Unlimited number of lines
- Allows editing of binary files
- Supports unix style text files (LF only)
- Limited undo
- Uses no CPU time when in the background
Installation
Copy the CEDIT.EXE file to a subdirectory of choice. Copy EDENGINE.DLL
to a directory in your LIBPATH (see your CONFIG.SYS), or add the
directory where EDENGINE.DLL resides to your LIBPATH.
If you have no idea about LIBPATH, etc., just copy the EDENGINE.DLL file
to the \OS2\DLL directory.
If you are installing over an older version of CEDIT, make sure that you
replace the old EDENGINE.DLL file.
If you want to make use of the save settings option (F5 S), add the
following line to your CONFIG.SYS to specify where the CEDIT settings
file should reside:
SET CEDIT_SETTINGS=d:\dir\cedit.ini
Example:
SET CEDIT_SETTINGS=C:\CEDIT\CEDIT.INI
CEDIT 1.1 DOCUMENTATION PAGE 2
Using CEDIT
Start CEDIT by typing CEDIT [filename.ext] at the OS/2 command prompt.
The filename is optional; if you do not provide a filename, you will be
prompted for one.
A few keys:
F1 - help (when in the editor)
F2 - show information about the current file and editor settings.
F3 - file menu
F4 - block menu
F5 - format menu
F6 - miscellaneous menu
F7 - print menu
F9 - shell to OS/2 command prompt
Ctrl-PgUp - goto beginning of file
Ctrl-PgDn - goto end of file
Alt-W - delete word right
Ctrl-W - delete word left
Alt-V - flip case to line end
Ctrl-V - flip case to line beginning
Alt-K - delete line
Alt-L - delete to line end
Ctrl-L - delete to line beginning
Alt-F - find forward
Ctrl-F - find reverse
Alt-F - continue find, forward
Ctrl-F - continue find, reverse
Alt-U - undo last deletes (up until last character was entered)
Alt-<num> - insert any ASCII character in text (except 0)
Alt-0 - insert null character in text (Use the zero on the main
keyboard, not the one on the numeric keypad)
CEDIT 1.1 DOCUMENTATION PAGE 3
Lazy screen updating
For performance, the screen is only updated when the editor is not busy.
This means that if you paste a large text (with OS/2's paste facility)
you will only see the cursor move and no text will appear while the
pasting is going on. This is perfectly normal and working as designed;
after the paste is completed the screen will be updated normally.
This effect can also be observed when scrolling through a file on a
computer with a slow video adapter.
More lines on screen
If you like, you can work in screen modes with more lines than 25. Just
use OS/2's MODE command (e.g. MODE CO80,50) to change the screen
resolution before starting the editor or inside the OS/2 shell (F9).
Editing UNIX style files
CEDIT will automatically detect if a file uses PC or UNIX style newline
characters (CR/LF or LF). You can see in the info screen (F2) if the
current file uses CR/LF or LF as a newline character. The <ENTER> key
will automatically insert the correct newline character.
To create a UNIX style text file, open a new file and type Alt-10, save
the file and reopen it.
Bugs
No bugs that I'm aware of exist in this release.
If you find any bugs, please contact the author (see How to contact the
author).
Thanks
Special thanks to Jason B. Tiller, Henk den Adel and Peter Struik for
their valuable feedback.
How to contact the author
If you have any questions, suggestions or bugs to report feel free to
contact me at one of the following addresses:
Internet: J.Frijters@ET.TUDelft.NL
CompuServe: 100120,72