Why use Ce and Ceterm

Ceterm is a terminal emulator like an xterm or hpterm or whatever, only
better.  
- NO reliance on screwy scroll bars that become difficult to work with
  when you have a large transcript.  (Scroll bar widget becomes very hard
  to get with your mouse-button and if it is close to top or bottom you
  wind up with a window-resize operation when you just wanted to move the
  scroll, etc.)
  
  Slow and fast scrolling is done with arrow keys for paging up and down
  (horizontal arrows do scroll horizontally).  Page-up and page-down keys
  work as well..
  
- Does NOT arbitrarily wrap lines.  With horizontal scolling you can always
  see a long line all the way to end..
  Can set the wrap if you wish.
  
- Treats all transcripts as a real FILE (thus takes virtually no process
  space or RAM for this unlike xterm/hpterm). 
  
- All transcripts are essentially infinite and are IMPOSSIBLE to scramble
  xterms and hpterms can easily scramble/destroy a transcript the minute
  you resize the WINDOW. (You may have spent the better part of an hour
  just getting an elaborate transcript out of a CAD tool that is not
  working right to show to the vendor..) then oops..
  CETERM would never screw up there.
  
- Transcript can easily be captured in its entirety. HPterms let you 
  capture the given window and xterm you have to carefully do a left-mouse
  at top, middle-mouse to scroll all the way to bottom, then right-mouse
  at bottom to capture whole.  CETERM just cntl-t to go to top, hit select
  key, and then cntl-b to bottom and you have a transcript captured that
  could easily be 2-5 megs or whatever.
  
- Exact same usage of at least 10-20 function key usage between the CETERM
  and CE.  So a copy/paste/selects all are identical between the CE-editor
  and the CETERM pad..  The term-pad is just a file handled by the SAME
  executable the takes care of your edits.  Typically in your /usr/bin
  the ceterm is just a LINK to the ce-edit executable!
  
  Not sure if I know of ANY other editor that has a companion TERMPAD
  that behaves the same as the editor-pads.  So THAT in my estimation
  is probably the MAIN claim to fame.
  
- CE/CETERM were both used heavily on Apollo.  HP even after taking over
  Apollo has dumped millions in WORTHLESS proprietary editors and terminal
  emulators.  Software people here knew that hpedit would easily crash
  and NEVER used it.  HP has junked all the VUE stuff and now has DT-stuff
  under HP10.20...  HP term-pads were junk, now they have dtterm and I 
  dont know if it is much better.
  
- Size of CE executable is only about 750K.  It is not a steam-shovel
  like Emacs.

- Easy rectangular cut and paste in editor or term-pad.

- A macro-capability and keys can be tied to macros.  Same macros
  work for both editor and term-pad of course.

Those are features just off the top of my head.. There are probably
more.

MORE:

            SOME FEATURES OF CE/CETERM

Ce-edit is a editor similar to one once in wide use on Apollos.

Ceterm is a terminal emulator like an xterm or hpterm or whatever, only
a lot better in some ways.


Some CETERM features are:

Many CETERM features are common to the CE-editor as well.

- Every CETERM or CE-edit pad has a BUILT-IN COMMAND line and this is apart
  from the INPUT-line in a typical term-pad.  You can type in a command-seq=
uence
  known to the CE tool by going to the command line with you cursor or by
  hitting the ESC-key.  This prevents having to switch between input and
  command 'modes' as with VI, and having to use escape sequences to do this=
.

- EXACT SAME USAGE of at least 10-20 function key usage between the CETERM
  and CE.  So a copy/paste/selects all are identical between the CE-editor
  and the CETERM pad..  The term-pad is just a file handled by the SAME
  executable the takes care of your edits.  Typically in your /usr/bin
  the ceterm is just a LINK to the ce-edit executable!
 =20
  Not sure if I know of ANY other editor that has a companion TERMPAD
  that behaves the SAME as the editor-pads.  So THAT in my estimation
  is probably the MAIN claim to fame.
=20
  Example of most-frequently used keys that behave the SAME for edit or ter=
m:=20
  F1 - starts SELECTION.  Just page-down or up to highlight or use vertical
       or horizontal arrow keys to highlight.
  F2 - COPY
  F3 - CUT/DELETE single line or delete whatever is currently highlighted.
       You cant delete from the middle of a term-pad as it is readonly but
       you can certainly delete stuff on the input-line of the term-pad.
  F4 - PASTE whatever was last cut or copied.
  F5 thru F12 - many other functions.
 =20
  Rectangular SELECT/COPY/CUT/PASTE is simply shift F1/F2/F3/F4 so you
  cant get much simpler than that. =20

- Very fast and easy to bring up a file in ceterm by just clicking on a=20
  file-name with the right-mouse button.  If you which these to always come=
=20
  up initially in read-only mode it is easy to set that for default=20
  operation.  If path is a directory it will tell you so, so this can also
  check validity of paths.  NOTE this operation is not reserved to just=20
  the term-pad but you can click on file paths in an edit-window and you
  get the same thing.  Even dollar-sign ENV variables are recognized/parsed=
.
 =20
- NO reliance on screwy scroll bars that can become difficult to work with
  when you have a large transcript.  (Scroll bar widget becomes very hard
  to get with your mouse-button and if it is close to top or bottom you
  wind up with a window-resize operation when you just wanted to move the
  scroll, etc.)
 =20
  Slow and fast scrolling is done with arrow keys for paging up and down
  (horizontal arrows do scroll horizontally).  Page-up and page-down keys
  work as well.  Newer versions of CE will give a scroll bar if you wish.
 =20
- Does NOT arbitrarily wrap lines.  With horizontal scrolling you can alway=
s
  see a long line all the way to end..
  Can set the wrap if you wish.
 =20
- Treats all transcripts as a real FILE (thus takes virtually no process
  space or RAM for this unlike xterm/hpterm).=20
 =20
- All transcripts are essentially infinite and are IMPOSSIBLE to scramble.
  With xterms and hpterms you can easily scramble/destroy a transcript the=
=20
  minute you resize the WINDOW. (You may have spent the better part of an
  hour just getting an elaborate transcript out of a CAD tool that is not
  working right to show to the vendor..) then oops..
  CETERM would never screw up there.
 =20
- Transcript can easily be captured in its entirety. HPterms let you=20
  capture the given window and with xterm you have to carefully do a left-m=
ouse
  at top, middle-mouse to scroll all the way to bottom, then right-mouse
  at bottom to capture whole.  CETERM just cntl-t to go to top, hit select
  key, and then cntl-b to bottom and you have a transcript captured that
  could easily be 2-5 megs or whatever.
 =20
- CE/CETERM were both used heavily on Apollo.  HP even after taking over
  Apollo has dumped millions in WORTHLESS proprietary editors and terminal
  emulators.  Software people here knew that hpedit would easily crash
  and NEVER used it.  HP has junked all the VUE stuff and now has DT-stuff
  under HP10.20...  HP term-pads were junk, now they have dtterm and I=20
  dont know if it is much better.
 =20
- Size of CE executable is only about 750K.  It is not a steam-shovel
  like Emacs. Process sizes are always small regardless of what is in
  the ceterm transcript pad.

- Easy rectangular cut and paste in editor or term-pad.

- A macro-capability and keys can be tied to macros.  Same macros
  work for both editor and term-pad of course.=20


CE-EDIT Features:
Some of these may be the same or similar to the terminal-features given
above. =20

- Same as CETERM.  Can easily bring up any file that shows up with a=20
  valid path in the edit window.  Easily check out validity of a
  path to a directory.  Single mouse click.

- Same as CETERM.  Rectangular SELECT/COPY/CUT/PASTE is simply 
  shift F1/F2/F3/F4.

- Easily edits extremely large files.  I have seen other editors
  bomb on large files.

- small process sizes regardless of what editor is doing.

- user can write own macros for easy inclusion in the single file that
  defines all the CE/CETERM keys and their actions.
 =20
Most of these features are just off the top of my head.. There are=20
probably others I have not thought of.


Possible drawbacks:
 - has a cost (about $250 a copy).
 - if you do a lot of things with old dyed-in-the-wool UNIX tools
   like the vi-editor and 'more', and these send control-character-sequence=
s
   to the screen, then your operation from a CETERM might be a bit
   scrambled.  You can throw ceterm into 'vt mode' to take care of most
   of this but it will probably never be completely smooth operation.