ARPUS/ce, Version 2.6.2 (03/10/05)    (SCCS 1.6)
_______________________________________________________________________________
 Concept:  Ce on Linux
 
 DESCRIPTION:
     Linux runs on PC type hardware and is very configurable. A set of
     Linux  key definitions is provided with Ce, but some  adjustments
     may be needed to get the desired results.

     For  Ce to work, X must be installed on the machine.  The ce_init
     command is used to build your initial .Cekeys file which contains
     all  the  key definitions.  Once that is in place, you should  be
     able to bring up Ce. Note that Ce must be run with the setuid bit
     set for root: chown root ce chmod 4755 ce

     The  key map you use on the Linux machine may vary depending upon
     where  you  get  the your X installation from and  what  make  of
     keyboard  you  use.   In general you use the xmodmap  command  to
     change  the  mapping  of  hardware key codes  to  X  key  symbols
     (keysyms).   On  one machine tested, the default keymap  for  the
     Delete  and BackSpace keys was the same.  They both mapped to the
     Delete  key.   The xmodmap command can be used to  rectify  this:

     xmodmap -e "keycode 0x16 = BackSpace"

     By  the way, do not execute the above command blindly.  The above
     hardware  keycode  may or may not be correct for  your  keyboard.

     This  change could be put in the .xinit file.  Ce can be used  to
     determine  the  mapping on the machine.  To do this, perform  the
     following steps:

     1.   In the Ce "Command:" window, enter the comamnd: 
          env CE_FULL_KK=1
          This will cause the hardware keycode information to be output
          when the kk (key key) command is executed.

     2.   Pick some key like "Insert" and enter the command:
          kd Insert kk ke
          This will make the Insert comand on the keyboard do a kk command.

     3.   Press the Insert key.  Nothing will happen.  The next key you
          press, withing that Ce window, will have it's data displayed
          in the message window.
          Ex:  Press Insert then Press the Delete key:
          Delete - keycode: 0x49, default er 7F
          The current X keysym name (name used in Ce kd commands) and the
          actual hardware keycode are listed.  Also, if that keysym has
          a literal value associated with it, it is listed.
          <X keysym> - kecode 0x<value>, default er <hex value>

     If  the displayed keysym is #0, then there is no name  associated
     with this key. You will need to use xmodmap to assign one. If the
     displayed  keysym  is  '#'  followed by  some  other  value,  the
     assigned keysym does not have a name, The #value can be used in a
     key definition but it must be in quotes:
     kd '#fffc302' pp .5 ke

     In  summary  some  tailoring  of   keys  on  a  Linux  system  is
     inevitable. The Ce kk command can be used to determine what these
     changes should be. If a key does not do what you think it should,
     use the 'kk' command to determine what it really is and check the
     definition  in  the  $HOME/.Cekeys file to determine what  it  is
     defined as.

     Useful Tips:

     The "bash" shell generates a lot of Curses control sequences. Use
     X resource:
     ceterm.man : y
     or start ceterm with the -man option.
     Another way of getting rid of control sequences in ls is to alias
     ls to be ls -o
     This  option  turns off the color highlighting which Ce does  not
     yet support.

     If  you use tcsh you will want to turn off the shell command line
     editor as it conflicts with ceterm. This is done with:
     unset edit

 
 RELATED HELP FILES:
     
     kd            (Key Definition)       
     kk            (Key Key)              
                   (Prompt)               
     commands      (List of Commands)     
     
     keyboard      (common keys)          
     keyCon        (Key Concepts)         
     xresources    (X resources & args)   

     support       (customer support)     

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