ARPUS/ce, Version 2.6.2 (12/14/05)    (SCCS 1.7)
_______________________________________________________________________________
 DESCRIPTION:
   X resources and command line options:

   Options  that  can be specified either on the command line or as  X
   resources  are  shown in both forms The option list  includes  some
   options which are meaningful only to ceterm. ce and cv accept these
   options, but they have no effect.

   In  the examples of X resources shown below, the class name "Ce"  is
   used.   Use of the class name causes the resources to be applied  to
   ce,  cv, and ceterm windows.  Command names ce, cv, and ceterm  may
   also be used in the .Xdefaults file in place of Ce. In addition the
   -name  parameter may be used to allow names other than those listed
   to  be  used.   Note  that the term ".Xdefaults file"  is  used  to
   represent  the  standard X resource lookup strategy which  includes
   the .Xdefaults file.

   The app-defaults file is setup during installation of Ce.  It needs
   to  be somewhere in the list of directories in the  XFILESEARCHPATH
   environment  variable and have the name Ce (upper case C lower case
   e).   If  the  environment  does  not  contain  an  XFILESEARCHPATH
   environment  variable,  the  Ce  app-defaults  file  should  be  in
   directory  /usr/lib/X11/app-defaults  which is the X  default.   Ce
   processes  the app-defaults file in a special way.  During  initial
   loading  and  -reload  processing,  the  Ce  app-defaults  file  is
   processed  according to normal X resource rules.  After the  normal
   processing,  the resources from the Ce app-defaults file are stored
   in  an  X  property.  During processing other than the  first  time
   through  or  -reload, ce reads the X property instead of the  file.
   This  technique  is  used   because  at   some   sites,  the  local
   app-defaults files were NFS mounted with automounter.  If more than
   5 minutes went by between bringing up Ce windows, the directory had
   to be remounted. This added a significant delay to bringing up a Ce
   window.

 -autoclose { y | n }
 Ce.autoclose:  { y | n }
        This  option  applies  only to ceterm windows.  If  set  to
        'yes',  the  window associated with the ceterm  process  is
        automatically closed when the ceterm process is terminated.
        If set to 'no' (the default), the ceterm window transitions
        into a ce window, with the ceterm's transcript pad becoming
        the ce session's edit text.  See the help file for 'pn' for
        details  on  saving the resultant ce session to a  specific
        file.
        DEFAULT:  n

  Ce.autocut:  { y | n }
        This  option, when set to 'yes', causes the 'ed'  (delete),
        'ee'  (backspace),  'es' (type a character), 'er'  (type  a
        special  hex  character),  and  'xp'  (paste)  commands  to
        automatically cut a highlighted area when they are in a key
        definition by themselves. That is, not part of a list of Ce
        commands  executed  under one keystroke.  This  provides  a
        behavior  similar  to  that seen in Netscape and  other  PC
        based editors.
        DEFAULT:  n

-autohold { y | n }
 Ce.autohold:  { y | n }
        This option applies only to ceterm windows.  If set to 'yes'
        ceterm  will automatically place the transcript pad in  hold
        mode  whenever  commands  run in the ceterm  shell  generate
        enough output to fill one ceterm window.  See the help files
        for  'wa'  and 'wh' for specific details on the behavior  of
        this feature.
        DEFAULT:  n

 -autosave n
 Ce.autosave: n
        If this option is enabled ('yes'),  ce  will  automatically
        update   the   file   changes   to  disk  after  every  'n'
        keystrokes.  This option has no effect on ceterm windows.
        DEFAULT:  no autosave

 -background <color>
 -bgc <color>
 Ce.background: <color>
        This  options  sets  the   background  color   to  <color>  on
        invocation.   <color>  must  be a valid color found in  the  X
        server's "rgb.txt" file or a hex color code. (The rgb.txt file
        is normally /usr/lib/X11/rgb.txt). <color> can be specified as
        either  the  color name, e.g., "light blue", or the color  hex
        code, e.g., "#bfd8d8".  If <color> contains embedded blanks or
        pound signs, it must be enclosed in quotes. Use of this option
        as  either  a parameter or an X resource overrides the  values
        specified in wdc commands in the .Cekeys file.
        DEFAULT:  white

 -bell {on | off | visual | VISUAL}
 Ce.bell : {on | off | visual | VISUAL}
        This  option  defaults  to  on.  Setting the  value  to  "off"
        suppresses  the  generation  of  an audible  beep  on  certain
        events.   Setting  the value to "visual" causes the window  to
        flash  reverse video instead of making a noise.  A lower  case
        "visual"  flashes  the  DM  message window.   An  uppper  case
        "VISUAL"  flashes  the main window.  Note that only the  first
        character of "on", "off", "visual", and "Visual" is examined.

 -bkuptype {dm | vi | none}
 -nb
 Ce.bkuptype: {dm | vi | none}
        Set the mode in which backup (.bak) files are created. 
        
        In 'dm' mode, the original file being edited is renamed  to
        <file>.bak,  and  a new <file> is created.  This means that
        any hard links  that  originally  pointed  to  <file>  will
        subsequently point to <file>.bak. 
        
        In  'vi'  mode, <file> is copied to <file>.bak.  This means
        that hard links  will  still  be  valid,  pointing  to  the
        changed  version  of <file>.  This technique is slower than
        creating the backup file via rename.

        Use 'none' if backup files are not wanted. The option -nb is
        equivalent to -bkuptype none.
        DEFAULT:  dm

 Ce.cekeys : <path>
        Path  to file containing site wide key definitions.   During
        key definition loading, Ce does an implied include (cmdf) of
        this  file  to  pick up site wide  definitions.   The  users
        personal  .Cekeys  file can override these.  The  lookup  is
        actually  a search.  First a check is made for the specified
        file  with  either  a '.A' or '.U' attached  depending  upon
        whether  the user is in Aegis regular expression mode (.expr
        resource) or UNIX regular expression mode. If that file does
        not exist, the name as specified in the file is checked for.
        This  allows for expression mode dependent key  definitions.
        You  can of course include (via cmdf) the base file from the
        expression mode specific files.
        DEFAULT:  Set at install time.

 -cmd "cmd;cmd;cmd"
 Ce.cmd:  "cmd;cmd;cmd"
       Use  this feature to have ce automatically execute a   series
       of   commands  when  it  starts up.  When used in a  resource
       file,  the 'cmd;cmd;cmd' string  must  not  be  enclosed   in
       quotes.     When   used   from   the   command   line,    the
       'cmd;cmd;cmd'  string MUST be enclosed in single  or   double
       quotes,    since  the  semicolon  ';'  is  a  special   shell
       character.   The string "cmd;cmd;cmd" can be  any  valid   ce
       command  sequence  that  is  acceptable  at  the "Command:"
        prompt. 
        DEFAULT:  none

 -display <display>
        Use  the specified <display>.  This must  be  a  valid  host
        name   a  display  designation  (such as "pluto:0.0").  This
        causes  the edit window to be displayed on the  named  host.
        It is useful when telneting onto a remote host to start a ce
        or  ceterm window and display it back on the workstation you
        are  sitting at.  Note that th X command xhost must be  used
        to  allow  other  nodes  or users to open  windows  on  your
        workstation.   
       DEFAULT:    $DISPLAY  (a   shell  environment variable).
                   This option cannot be set in the .Xdefaults file.

 -dpb <name>
 Ce.dfltPasteBuf : <name>
        Use  the  specified  name as the default paste  buffer.   As
        delivered, this is the paste buffer name CLIPBOARD.  This is
        the default paste buffer name for most Sun applications. The
        other common name is PRIMARY with is the name used xterm and
        other  applications.   This resource is commonly set by  the
        system  administrator to the value PRIMARY in the app-defaults
        directory file "Ce".
        DEFAULT:    CLIPBOARD

 -dotmode {0 | 1[string] | 2}
 ceterm.dotmode : {0 | 1[string] | 2}
     The  ceterm  password  dot  mode option  is  needed  on  HP/UX
     machines of release 10.20 and beyond where the users primarily
     use the csh shell. When ceterm detects that the user is typing
     a  password,  the program goes into dot mode.  The  characters
     typed  are displayed as dot's and undo processing is  disabled
     so  you cannot undo to get the password back.  At HP/UX 10.20,
     it  was  not  possible to find a combination of  tty  settings
     which  would  correctly  indicate that a  password  was  being
     entered  for  the  csh (ksh works fine).  To rectify  this,  a
     simpler  method  of   detecting  password   prompting,  namely
     watching  for  "pas" in the prompt string (case  insensitive),
     was  added.   In this mode, you can optionally set the  prompt
     fragment to look for.
     VALUES:
     0  -  Nodot mode, never display dots, passwords are visible
     1  -  Scan prompt for string,  Note, if you use hostname in your
           UNIX prompt and your node name is Pascal, you are sunk.
     2  -  Normal mode, watch the tty bits to determine password entry.
    DEFAULT:    2 (Can be set during installation)

 -expr {Aegis | Unix}
 Ce.expr: {Aegis | Unix}
        Ce  understands  both  Aegis  and  Unix  regular  expression
        syntax.   See the regular expression help file regexpCon for
        full  details  on AEGIS and Unix regular expressions.   This
        option  is  normally  set  in the .Xdefaults  file  and  not
        overridden.   Key  definitions,  which  often  have  regular
        expression searches in them, are written either for Unix mod
        or Aegis mode and will not function properly under the other
        mode.   If a user has compiled an Apollo key definition file
        to run under Ce in Aegis mode, a conversion to Unix mode may
        be  aided by starting a ce session specifying -expr Unix and
        executing  the  keys  command   in  that  window.   The  key
        definitions  will  be  decompiled into kd commands  in  Unix
        mode.   This  will convert all definitions except those  key
        definitions  which redefine keys and use regular expressions
        in the redefining definition.

        Warning:  The .Xdefaults file is normally run through the  C
        preprocessor when it is read in. On many machines the string
        "unix"  is a macro whose value is "1".  Ce attempts to  flag
        this situation as an error. Thus it is preferable to specify
        unix as "U" or "Unix" instead of "unix".
        DEFAULT:  Aegis

 -envar {Y | N}
 Ce.envar: {Y | N}
        This  parameter  controls   the  processing  of  environment
        variables  found  in path names for the cv and  ce  commands
        executed in the "Command:" window. When set to yes, clicking
        on  a name such as $HOME/.profile will expand $HOME.  It  is
        possible  to  escape  the dollar sign on the name  to  avoid
        expansion  if the cv command is being typed in as opposed to
        being  generated  by clicking on the name.  When set to  no,
        dollar  signs  are ignored.  This allows clicking  on  names
        which contain dollar signs.
        DEFAULT:  Yes

 -findbrdr <num>
 Ce.findbrdr: <num>
        Use the specified number as a border for find commands. That
        is,  make  sure  there are <num> lines between  the  top  or
        bottom  of the window and the found string.  This is ignored
        if the find is in the first <num> lines of the file.  It may
        be  modified  if the number of lines in the window  is  less
        than  double num.  This option is often set to 1 or 2 in the
        .Xdefaults file.  For example: If the resource Ce.findbrdr:1
        is  active,  a the find command will position the window  so
        there  is at least one line of text above or below the found
        line.
        DEFAULT:  0

 -font <font>
 Ce.font: <font>
        Use  the  specified <font>.  <font> must be a valid X  font
        that would be listed via the 'xlsfonts' command. The use of
        variable-width  fonts  is  discouraged  as  it  will  cause
        rectangular highlighting operations to look funny. To see a
        list  of  fonts  available  on  your  workstation  execute:
        /usr/bin/X11/xlsfonts | cv
        DEFAULT:  fixed

 -foreground <color>
 -fgc <color>
 Ce.foreground: <color>
        This  options  sets  the  foreground  color  to  <color>  on
        invocation.   <color>  must be a valid color found in the  X
        server's  "rgb.txt" file or a hex color code.  (The  rgb.txt
        file  is  normally  /usr/lib/X11/rgb.txt).  <color>  can  be
        specified  as either the color name, e.g., "light blue",  or
        the  color  hex code, e.g., "#bfd8d8".  If <color>  contains
        embedded  blanks  or  pound signs, it must  be  enclosed  in
        quotes.   Use  of this option as either a parameter or an  X
        resource  overrides the values specified in wdc commands  in
        the .Cekeys file.
        DEFAULT:  black

 -geometry [c]<geometry>
 -g [c]<geometry>
 Ce.geometry: [c]<geometry>
        This  option specifies the size and shape of the Ce  window.
        The   form   is  <width>X<height>[{+|-}<x>{+|-}<y>].     The
        leading   'c'  is optional.   If  specified,  ce  interprets
        the   width   and  height  geometry  values   as   character
        columns  and  rows instead of x and y pixels. If 'x' and 'y'
        are  both  positive, they specify the pixel position of  the
        upper left corner of the ce window with respect to the upper
        left  corner  of  the display.  If both are  negative,  they
        specify  the pixel position of the lower right corner of the
        ce  window  with  respect to the lower right corner  of  the
        display.   For  example: 400x500+10+25 creates a window  400
        pixels wide by 500 pixels tall with the upper left corner of
        the  window 10 pixels from the left edge and 25 pixels  from
        the  top edge of the display.  Note that the window  manager
        may  override the requested value.  c80x24-10+25 will create
        a  window  80 columns wide by 24 rows tall in the  requested
        font.   The  upper  right corner of the window  will  be  10
        pixels  from the right edge of the screen and 25 pixels from
        the  top.  Use of this option as either a parameter or an  X
        resource  overrides the values specified in wdf commands  in
        the .Cekeys file.
        DEFAULT:  none

 -help
        This option causes Ce to print a summary of the command line
        options  and  exit.  This option is not available  from  the
        Command: prompt.

 -ib <path_name>
 Ce.iconBitmap : <path_name>
        This  option causes Ce to use the requested file as the bitmap
        for the icon.  The file should be in the format created by the
        X bitmap utility.  This utility is found in different places
        on different types of machines.
        DEFAULT: The standard ce/ceterm icons  

 -iconic
 Ce.iconic : {y | n}
        This  option causes Ce to communicate to the window  manager
        that  it  is to be started as an icon instead of  a  window.
        This is useful in the xinitrc startup script. The X resource
        version of this option should be used with great care.
        DEFAULT:  Open as a normal window.

 -isolatin { y | n }
 -is { y | n }
 Ce.isolatin: { y | n }
        If  this option is set to 'yes', isolatin characters can  be
        entered using the required modifier keys. Since the modifier
        keys  vary from system to system, you will need to refer  to
        your  system's  documentation  for  specific  details.   The
        purpose of this option can be seen by the following example.
        On  many  HP/UX  keyboards, the  <extend-char>h  combination
        yields  the  Yen symbol when using an isolatin font.   If  a
        non-isolatin  font  is  used, it generates  a  non-printable
        character.   If a user is making use of the special  symbols
        and  European characters accessed via the <extend-char> key,
        it  is  desirable  to  insert the  code  for  these  special
        characters  into  the file just as if they were  a  standard
        character. However, if one is using an American font and not
        using these characters and there is no Ce key definition for
        *yen,  it is desirable to do nothing.  This makes the action
        consistent  with pressing *F2 when *F2 has not been defined.
        This  option is normally set as an X resource in either  the
        users .Xdefaults file or in the /usr/lib/X11/app-defaults/Ce
        file.

        DEFAULT:  no

 -kdp <name>
 Ce.keydefProp : <name>
       Ce stored the key definitions it reads from the $HOME/.Cekeys
       file in an X property hung off the root window. This property
       allows  a  different name to be used.This option can be  used
       with  the -name option or aliasing the ce command to maintain
       multiple  sets  of independent key definitions for  different
       windows.   This falls under the heading of extremely advanced
       features.   It  has  been used in  writing  simulators  which
       control  bunches of ce and ceterm windows simulating multiple
       processors.   Related  to  this property is  the  environment
       variable CE_KDP. If the -kdp argument is NOT specfied and the
       CE_KDP  environment variable is set, the property is set from
       the  environment  variable.  There are cases where  a  person
       wants  to   use   different  key   definitions   for  windows
       originating  on a particular machine.  By setting the  CE_KDP
       environment  variable  in  the .profile for that  machine  to
       other  than the default value, ce and ceterm windows  started
       on that machine will use key definitions from a $HOME/.Cekeys
       file on that machine.  If you do this, you are on your own as
       far  as keeping track of which windows are using which set of
       key definitions.
       DEFAULT:    CeKeys

 -linemax <num>
 Ce.linemax: <num>
        This option can cause Ceterm to limit the number of lines it
        retains in the transcript pad.  By default, the upper limit
        is approximately 16 million lines.
        DEFAULT:  Unlimited

 -lineno { n | y }
 Ce.lineno: { n | y }
        If  this is set to 'y', file line numbers are shown  along
        the  left margin.  This option may be turned on or off after
        the ce window is opened via the lineno command.
        DEFAULT:  n

 -load
        When ce is first invoked during a new login session, it must
        parse your key definitions file and store the definitions in
        the X server database. Files containing many key definitions
        may take a few seconds to process.  You can avoid that delay
        by putting the command 'ce -load' in your '.profile' startup
        file.   The  '-load'  option tells ce to  process  your  key
        definitions  file,  store  the definitions in the  X  server
        database,  and  terminate  without opening an  edit  window.
        Subsequent ce commands will create the edit window much more
        quickly since the key definitions are already loaded.

 -lockf { y | n }
 Ce.lockf : { y | n }
        Ce supports the use of System V, advisory file locking.  The
        default  is  to  use file locking.  Specifying  'n'  in  the
        command  line  argument or the X resource disables the  file
        locking feature. Note that file locking is only supported on
        file  systems  which support advisory locking via the  lockf
        system call.  This includes local files systems and most NFS
        file systems.
        Default: Y

 -ls
 ceterm.loginShell : {y | n}
        This  option indicates that the shell that is started in the
        ceterm window be a login shell (i.e.  the first character of
        argv[0]  will  be  a dash, indicating to the shell  that  it
        should read the user's .login or .profile).

 -lsf { n | y }
 Ce.lsf: { n | y }
        If  this is set to 'y', the language sensitive filtering is
        enabled.  This allows ce to perform file type specific 
        functions identified in the $HOME/.Cetype file.
        DEFAULT:  n

 -man
 ceterm.man: {no | yes}
        Numerous  systems  have  'man' pages that  contain  embedded
        backspaces  for the sake of underlining and other expressive
        text  constructs.   ce normally does not  process  backspace
        characters  specially,  making files that contain  backspace
        characters difficult to read.  You can use the '-man' option
        to  tell ce to eliminate those backspace characters and  the
        accompanying  'overstrike' characters to make the file  more
        readable.   This  option is commonly used when  setting  the
        PAGER  environment variable.  For example: 'export PAGER="cv
        -man"'  from a ksh will cause the man(1) command to  display
        the manual page in a cv window just like on an Apollo domain
        system.   On  some machines, man does not look at the  PAGER
        variable,  in  which case a shell named man, which runs  the
        man  command and pipes it into cv can be used to achieve the
        same end. When -man is used in a ceterm, it causes ce to eat
        any  vt100  control  sequences which are sent to it  by  the
        shell. It is recommended that the X resource version of -man
        only  be  used with ceterm, as it modifies the way  data  is
        loaded by Ce.

 -mouse {on|off}
 Ce.mouse:  {on|off}
        This  resource  tells ce how to coordinate the text  cursor
        with the mouse cursor.  The default behavior (Ce.mouse: on)
        is  for  the  cursor to follow each other:  when  the  text
        cursor  moves, the mouse cursor follows it, and vice versa.
        If  the mouse cursor is moved and text is entered, the text
        appears  at  the  mouse cursor's  current  position.   When
        Ce.mouse is set to 'no', the cursors move independently. If
        the mouse cursor is moved, the text insertion position does
        not  change.  This behavior works in concert with the 'sic'
        command,  which  tells  ce to move the text cursor  to  the
        mouse  cursor's  current position.  See the help  file  for
        'sic'.
        DEFAULT:  on

 -name <name>
        This  option  specifies the application name under  which  X
        resources  are  to  be  obtained, rather  than  the  default
        executable  file name and the class name Ce.  <name>  should
        not contain ``.'' or ``*'' characters. For example: If -name
        pogo  was  specified, X resources from the  .Xdefaults  file
        starting "pogo." would be used in place of "ce.", "cv.", and
        "ceterm.". "Ce." resources would still be found. This option
        can  also  affect  the way the window manager  manages  your
        window.   For example, specifying -name MAILBOX and  putting
        the  line  "Mwm*MAILBOX*clientDecoration: minimize"  in  the
        .Xdefaults  file would cause the Motif window manager to use
        minimal border decorations when reparenting this window.

 -noreadahead
 Ce.noreadahead: {y | n}
       Normally,  ce reads in enough data from the file being edited
       to  display the first screen, displays the screen, and spends
       the  time  in  between  user actions reading the  file  in  a
       background mode.  The -noreadahead parameter instructs ce not
       to  do  this and only read in data as it is needed.  This  is
       useful when looking at the top few lines of very large files.
        DEFAULT:  Read file in background mode.

 -offdspl { y | n }
 Ce.offdspl: { y | n }
        This  option  overrides a normal "safety" feature of Ce  for
        use with virtual window managers such as olvwm.  Normally Ce
        will  not allow the specification of a window geometry which
        has no portion of the window visible. This is because such a
        window  is  very difficult to interact with.  When  using  a
        virtual  window manager it may be desireable to bring up  Ce
        windows  in  parts  of the virtual workspace which  are  not
        currently  visible.   This is especially true  during  login
        startup processing. When set to 'y', the offdspl argument or
        X  resource allows the specification of geometries which are
        off screen. Whether this option is required depends upon how
        the virtual desktop is managed.  Managers such as HP/VUE and
        CDE  unmap  the  windows  which are  not  in  the  currently
        displayed  desktop.   Window  managers like olvwm  move  the
        window  to geometry values which are off screen.  It is  for
        this  second type of window managers that the offdspl option
        is supplied.
        DEFAULT:  n

 -oplist
      The causes Ce to calculate it's run time options and dump them
      to stdout.  It is useful in diagnosing problems and is used in
      the procedure which updates Ce from a previous release.

 -padding n
 Ce.padding: n
       You can use this option to  specify  the  amount  of  space
       between  lines  in the edit window.  "n" is an integer that
       is a percentage of the height of the  window's  font.   For
       example,  if  the font's height is 15 pixels and 'n' is 40,
       the space between lines is 15 * 40% = 6 pixels. 
       DEFAULT:  0 (meaning, 0 PERCENT)
       THIS PARAMETER IS DEPRECATED AND WILL BE REMOVED IN THE
       NEXT RELEASE.
       

 -pbd <directory>
 Ce.pasteBuffDir: <directory>
       Use  the specified <directory> to hold paste buffer  files.
       The  default  paste  buffer directory resides  in  /tmp,  a
       generally  public  area.  If you need to use  secure  paste
       buffers, specify a directory within your home directory.
       DEFAULT:  ~/.CePaste

 -pdm {y | n}
 Ce.pdm : {y | n}
      The  pdfm  or  the X windows resource ".pdm" can  be  set  to
      define whether the pull down menu bar is initially visible or
      invisible.  It is common to have the pulldown menu bar on for
      ce and cv and off for ceterm:
      ce.pdm : y
      cv.pdm : y
      ceterm.pdm : n

 -reload
       This  option  tells  ce to reload your key definitions into
       the  X  server  database  even  if  the  database   already
       contains  your  key  definitions.  This option forces the X
       server to accept a  new  set  of  key  definitions  and  is
       useful   if  you  are  experiencing  problems  with  the  X
       server. 

 -readlock
      This  option  tells  ce to operate in read  only  mode  and
      disables the ro command. Thus you cannot toggle out of read
      only mode in that window.  This feature is used by programs
      which  invoke  Ce  and do not want the user to  enter  edit
      mode.

 -sb {y | n | auto}
 Ce.scrollBar : {y | n | auto}
      Scroll  bars  are always on (y), off (n), or they  appear  as
      needed.  As needed is defined as a vertical scroll bar exists
      when  the number of lines being displayed exceeds the  number
      of  lines  in the window.  A horizontal scroll bar is  needed
      when a line is longer than a window.  A special note about Ce
      horizontal  scroll bars: The slider width is an indication of
      the width of the window with respect to the width of th line.
      To facilitate horizontal scrolling, Ce operates as though the
      line  width  is at least 300 characters when the  scroll  bar
      slider  is   drawn.    This   can  be   modified   with   the
      Ce.scrollBarWidth option. Note also that the scrollBar option
      is  often set differently for ce and ceterm.  It is common to
      turn it off in ceterm windows.
      Ce.scrollBar : auto
      ceterm.scrollBar : no
      DEFAULT:    auto

 -sbwidth <num>
 Ce.scrollBarWidth : <num>
      The    argument    sbwidth   or  the   X   Windows    resource
      "scrollBarWidth"  can  be set to define the minimum line  size
      used  to calculate the dimensions of the slider portion of the
      scroll  bar.  For example: If the window is 80 characters wide
      and  one  of the lines displayed is 160 characters  wide,  the
      horizontal scroll bar slider will be one half the width of the
      gutter it rides in. This allows you to slide to the end of the
      line  with the slider.  The use of horizontal scrolling in  Ce
      makes  this somewhat restrictive.  It would be nice to use the
      horizontal  scroll  bar  to move farther than the end  of  the
      line. To facilitate this, the scrollBarWidth resource is used.
      If  the  horizontal  scroll bar is displayed,  it  behaves  as
      though  the longest line displayed is at least  scrollBarWidth
      characters long. If a real line is longer, the longer value is
      used. Setting scrollBarWidth to 1 will make the slider size to
      the  longest line in the window.  Setting scrollBarWidth to  0
      disables the horizontal scroll bar.  This way you can use just
      the vertical scroll bar without ever seeing the horizontal.
      DEFAULT:    300

 -sc {no | yes}
 Ce.caseSensitive: {no | yes}
      This option specifies whether search operations done via the
      find  (/)  and  reverse  find (\) command  are  to  be  case
      sensitive  (yes) or case insensitive (no).  case sensitivity
      can  be  changed  via the ce 'sc'  command.   The  searching
      performed in substitute commands is always case sensitive.
      DEFAULT:  no

 -scroll {no | yes}
 Ce.scroll:  {yes | no}
      This feature controls the scrolling behavior  of  a  ceterm
      transcript  pad.  When enabled, output is scrolled one line
      at a time.  Otherwise the output is scrolled one window  at
      a  time.   See  the  help  file  for  the  'ws' command for
      details on setting this value from within a ce session. 
      DEFAULT:  yes

 -stdin
      This  option instructs ce/ceterm to accept dm commands  from
      stdin.   This option is invalid if ce is being instructed to
      read  its  text file from stdin because no file to edit  was
      specified. This option is useful if ce is being popen'ed(3).
      DEFAULT:  stdin is not watched for commands.

 -tabstops "ts [s1 [s2 ... sn] [-r]]"
 Ce.tabstops: ts [s1 [s2 ... sn] [-r]]
      Set  tab stops in columns 's1, 's2', ..., 'sn'.  If '-r'  is
      present,  add  additional  stops  spaced  according  to  the
      difference  between  the last two specified stops.   If  the
      command  line  option  is  given, the 'ts'  command  in  its
      entirety  must be enclosed between single or double  quotes.
      If  the resource file form is used, quotes must be excluded.
      See the 'ts' help file for complete details.

 -title "title string"
 Ce.title:  title string
      This  option  sets  the window manager's  windows  title  to
      "title string". (The window title is one of the Motif window
      decorations,  whose inclusion or exclusion can be controlled
      via  the   mwm   (Motif  window   manager)  clientDecoration
      resource.)  If used within the resource file, 'title string'
      should  not be enclosed in quotes.  If used from the command
      line,  'title  string'  should be enclosed in quotes  if  it
      contains white space.
      DEFAULT:  ARPUS/ce, Version 2.4

 -transpad
      This  option puts a ce window into a special read from stdin
      mode. It is useful when piping into ce from a device such as
      a  hardware monitor which generates data sporadically over a
      long  period of time.  When Ce is running in its normal mode
      and  it is reading from stdin, if you press ^b (go to bottom
      of  file), the screen will lock until all the data has  been
      read  in  so that the bottom of the file has been  read  in.
      This is fine when using Ce as a pager for manual pages. When
      displaying  output  from  some  device  which  is  producing
      messages,  a behavior like the transcript pad of a ceterm is
      desired,  only  with no UNIX command window.  The  -transpad
      option  provides this behavior.  One use for this option has
      been  to  provide  a monitor window in a debugger.   The  ce
      program  was  executed  via a 'C' popen(3) call  and  output
      written to this pipe as needed.
      DEFAULT:  Off
        
 -ut
 Ce.utmpInhibit : {True | False}
      This  options  performs  the same function as the  xterm  -ut
      option.   It affects ceterm only.  Normal operation calls for
      ceterm  to  generate a Unix utmp entry which is viewable  via
      the Unix who(1) command.  Specifying this option inhibits the
      generation  of the utmp entry.  On some platforms, specifying
      -ut  allows a ceterm to be started without the program having
      special setuid privileges.
      DEFAULT:  (False) Generate a Unix utmp entry.

 -version
      This   option  causes Ce to it's version identifier and exit.

 -vcolors "c1,c2,...c8"
 Ce.vcolors: brown,red,#00aa00,yellow,blue,magenta,#00aaaa,gray
      Colors for vt100 colorization, 8 comma separated values. The
      sample  above  is the default which matches the deault in  a
      Linux  Gnome terminal.  These colors correspond to the vt100
      graphic  renditions 30 to 37 and 40 to 47 in reverse  video.
      Each color can be a color name such as red or a '#' followed
      by  6 hex digits representing the RGB (red green blue) color
      values.   In addition each comma separated item may  contain
      two  colors  separated  by  a  slash  ('/').   For  example:
      brown,red/blue,#00AA00  In  this  case, the  second  graphic
      rendition  is  set  to use a background color of red  and  a
      foreground  color  of blue.  Thus a graphic rendition of  31
      will  color  blue  on  red and  the  reverse  video  graphic
      rendition of 41 will color red on blue.


 -vt {on | off | auto}
 Ce.vt:  {on | off | auto}
      This option applies only to ceterm windows. If set to 'auto'
      ceterm  will  automatically   enter  vt100   emulation  mode
      whenever  the shell requests that the "echo" line discipline
      is  disabled.  This more accurately reflects the behavior of
      the terminal windows on an Apollo Domain system. Use of this
      feature  will  cause ceterm to enter vt100 mode  whenever  a
      password  is being requested and whenever a telnet or rlogin
      is performed. The value "auto" disables the toggle action of
      the "vt" command.  The value "on" will cause ceterm to start
      in  vt100 emulation mode.  The value "off" will cause ceterm
      to  start  in normal mode.  The "vt" command may be used  to
      change this state on the fly.
      DEFAULT:  off
        
 -w
      Normally  the 'ce and 'cv' shell commands spawn a  separate
      editor  process,  and the shell in which the command  gives
      the prompt for the next command. -w instructs the editor to
      not  return  control to the shell until you close the  edit
      window.   This allows you to use this editor inside a  mail
      program.
      DEFAULT:  spawn a child process and return immediately

 -wmadjx <num>
 -wmadjy <num>
 Ce.wmAdjustX: <num>",
 Ce.wmAdjustY: <num>",
      Some  window  managers, notably the Sun olwm adjust  window
      position  requests  by  a fixed offset.  When a  Ce  window
      closes, it saves its geometry.  If the next Ce window opens
      without  specifying  a  geometry   via  a  parameter  or  X
      resource,  the window will be put in the same place as  the
      one just closed.  If the window manager is adding constants
      to  the  requested geometry, the window will  slowly  creep
      across  the screen as the window is opened and closed.  The
      Ce.wmAdjustX  and   Ce.wmAdjustY   options  are   used   to
      compensate for this effect.
      DEFAULT:  0
      For olwm try:
      Ce.wmAdjustX : -4
      Ce.wmAdjustY : -25

 -XSync  {no | yes}
 Ce.XSynchronize : {no | yes}
      The XSychronize resource, when yes, turns on the like named
      X11  service.  On some Xterminals, this prevents crashes in
      the  X  server.  However, on dialup PPP  connections,  this
      makes  things  very  slow.  Use this option if you  use  an
      Xterminal and are having trouble with the X server hanging
      or crashing.
      DEFAULT:  no


 -xrm "resource:value"
      The  xrm option allows the specification of X resources.  This
      is  a  standard  parameter  for X  applications.   It  is  not
      especially  useful  with  Ce,  as all  the  resources  can  be
      specified  from  the command line.  The parameter holds one  X
      resource  line.  The -xrm parameter may be specified  multiple
      times. For example: -xrm "ce.foreground:red"

 Ce.LSHOST:  <node_name>
      This  option assists in the use of the license server.  The
      license  server client code checks the environment variable
      LSHOST to find the node running the license manager. If the
      environment  variable is NOT set in the environment at  the
      time Ce is started, the value in this resource is placed in
      the  environment for use by the license server client code.
      This  option is usually set in the app-defaults file for Ce
      by  the  system  administrator.  Note that  if  the  LSHOST
      variable is set in the environment, this value is ignored.
      DEFAULT:  NULL (Can be set during installation)
                    
 -CEHELPDIR <path>
 Ce.CEHELPDIR : <path>
      The  CEHELPDIR  resource  is set in the  installation  of  the
      app-defaults  file  for Ce to the directory containing the  Ce
      help  pages.   If  you  do not set  the  environment  variable
      CEHELPDIR  in  your  .profile,  Ce will use  this  value  when
      looking  for the help pages.  This technique makes the Ce help
      file directory easier to move around.


   ce,  cv,  can  ceterm   can  distinguish   their   own  X  resource
   specifications. If you want a resource specification to apply to cv
   only, use "cv.<resource>" instead of "Ce.<resource>".  For example,
   if  you want ce and cv to use a light blue background, but you want
   cv  to  use  white foreground and ce to use black  foreground,  the
   appropriate resource specifications would be
   
       Ce.background: light blue
       ce.foreground: black
       cv.foreground: white
   
   By  creating soft link aliases for ce in your $HOME/bin directory,  you
   can  have many sets of defaults based on the command name you use.  The
   -name  option can also be used for this purpose.  Note that you  should
   avoid using dots in the name (ex: ce.mine) because the dot confuses the
   standard  X11  parser  which  is  used  to  process  the  command  line
   arguments.

 RELATED HELP FILES:
    cv            (Create View - Command: prompt)       
    ce            (Create Edit - Command: prompt)       
    cc            (Carbon Copy)                         
    cp            (Create Process)                      
    cpo           (Create Process Only)                 
    cps           (Create Server Process)               

    commands      (List of Commands)                    

    keyboard      (Common Keys)                         
    xdmc          (Execute DM Commands)                 
    ceterm        (ceterm - from shell prompt)          
    regexpCon     (regular expressions)                 
    
    support       (customer support)                    
        

_______________________________________________________________________________
  Copyright (c) 2005, Robert Styma Consulting.  All rights reserved.