🚀 go-pugleaf

Firstly, expert users of BASH (GNU's Bourne Again SHell) will
be able to give you solutions to all these problems.
Meanwhile, if you must with ksh....

In <1992Jul21.183727.20364@gmuvax2.gmu.edu> rjackson@gmuvax2.gmu.edu (Richard L Jackson Jr) writes:

>I did a simple comparison of CSH and KSH.  I am asking this
>group for solutions to csh feature that ksh appears to lack.
>I am using ULTRIX 4.1, VAX 8530.

>1) set filec or file completion
On the command line, go into the vi-editing mode (I don't know how to do
this in emacs mode), and place the cursor on the name of the file you want to 
expand. Hit '*' which will expand the current filename as if '*' were 
appended to it. Or hit '\' and the current word will be replaced with 
"the longest common prefix of all filenames matching the current word with
an asterik appended." There's a bunch of other nifty things... These features
are present in BASH also.


>2) concurrent sessions inadvertently use the same history
>   file.  Appending a pid to the history file at login may help
>   but there is no logout facility to remove the file.

With KSH you can trap signals and execute programs on reception of
those signals. I've seen someone trap the EXIT  
signal (or something like that) and have it run a shell, which
did exactly that -- it removed a process-dependent sh-history file.
Sometimes the shell was terminated abnormally and hisotry files
would build up. So it's good to put them into a directory and
once a week clean them out.

>3) how does one invoke a .logout script at ksh exit?
See above.


-- 
 --------------------------
|Timothy J. Shelling, CmpE |"Paired opposites define your longings --
|  tim@mal-s2.gatech.edu   |  and those longings imprison you."
| gt2540b@prism.gatech.edu |				    -- Zensunni Whip