Gfx and user interface

CDE, HP-UX >= 10.20

DTSOURCEPROFILE=true

VUE, HP-UX <= 10.20

1. in $HOME/.profile's and /etc/d.profile (the default user profile):

   if [ ! "$DT" -a ! "$VUE" ];
   then
      ...          # here all stty, tset commands etc
   else
   . /etc/profile  # common profile execution in case of VUE
   fi
   

2. in all $HOME/.vueprofile's individually activate the line with

   VUE=true; ...
   

   and, if applicable, adapt

   PATH=$PATH:.....
   

3. Scrollbars for terminal windows:
   If not existing yet:

   cp /usr/lib/X11/app-defaults/HPterm.ad /usr/lib/X11/app-defaults/HPterm
   

   In the files /usr/lib/X11/app-defaults/XTerm and /usr/lib/X11/app-defaults/HPterm, respectively:

   xterm*saveLines:      4s
   xterm*scrollBar:   True
   HPterm*saveLines:      4s
   HPterm*scrollBar:   True
   

   where 4s specifies lines to be saved "four screens" deep. Note that then /usr/lib/X11/app-defaults/%N must appear in the XFILESEARCHPATH.
   See also the legacy FAQ how to handle VUE-specific actions.
4. Use of arrow keys for command line editing (hpterm,ksh):
   Found various recipes, none of which worked:
   • Discussion in HP's ITRC forum
   • excerpt from a tcsh FAQ:
     14. How can I use the arrow keys with hpterm?
     Hp terminals use the arrow keys internally. You can tell hpterm not to do that, by sending it the termcap sequence smkx. Since this has to be done all the time, the easiest thing is to put it as an alias for precmd, or inside the prompt:

        if ($term == "hp") then
            set prompt="%{`echotc smkx`%}$prompt"
        endif
     

     Note that by doing that you cannot use pgup and pgdn to scroll... Also if you are using termcap, replace "smkx" with "ks"...
   • found in Usenet (Mike Stroyan, comp.sys.hp.hpux):
     

       hpterm has two modes for the behavior of the arrow keys.  The default,
     keypad_local mode, moves the cursor around the window as you see.  The
     keypad_xmit mode sends escape sequences when you press the arrow keys.
     Those escape sequences can be interpreted by an editor or the shell.
     
       You can change the mode using the escape sequences output by
     "tput smkx" for starting keypad_xmit mode and "tput rmkx" for starting
     keypad_local mode.  The vi editor already uses those sequences,
     returning the arrow keys to keypad_local mode when it finishes.  To use
     keypad_xmit mode in a shell, you potentially need to get the smkx escape
     sequence output after every command.  You can do that by putting the
     escape sequence in the shell prompt string.  For posix-sh you could to
     that with PS1="$PS1$(tput smkx)".
     

X server (HP-UX 11.x, 10.20)