home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os9
- Path: sparky!uunet!spool.mu.edu!uwm.edu!cs.utexas.edu!milano!cactus.org!cheselka
- From: cheselka@cactus.org (Michael R. M. Cheselka)
- Subject: Re: Information on OSK
- Message-ID: <1992Nov11.074353.12552@cactus.org>
- Organization: Capital Area Central Texas UNIX Society, Austin, Tx
- References: <EeyxRFm00WB4Nh9moE@andrew.cmu.edu>
- Date: Wed, 11 Nov 1992 07:43:53 GMT
- Lines: 29
-
- In article <EeyxRFm00WB4Nh9moE@andrew.cmu.edu> rh2y+@andrew.cmu.edu (Russell E. Hoffman, II) writes:
- >Excerpts from netnews.comp.os.os9: 7-Nov-92 Re: Information on OSK by
- >ferguson ct 71078@x102a.
- >> I tinkered with the bourne shell for a while (and gave up) and the
- >> following is from memory. First of all, the command line editing did
- >> not work completely unless 'sh' was the login shell. When executed as
- >> a subshell to a 'shell' parent, only a few of the command line editing
- >> commands worked. Command history did not work at all unless 'sh' was
- >> the login shell.
- >
- >Not so. If you have a .profile file in your home directory (specified by the
- >environment variable $HOME), containing the single line
- >
- >history 40
- >
- >(or some other integer number of lines of history to save)
- >
- >then sh will read the .profile file and start history up whenever your run sh.
- >If you look in the TOP stuff, there is a help file on sh, but I think
- >it's in a wierd place, like in the CMDS directory.
- >
-
- I wish people would stop refering to the shell as 'sh', because it is an
- early version of 'bash'...the Gnu 'Bourne Again SHell'.
- --
- cheselka@cactus.org N5UVV Michael R. M. Cheselka
- os9@gnu.ai.mit.edu Hangs out on 145.21mhz 400 W. 34th st. #103
- membership@cactus.org Austin, TX 78705-1331
- {...}!cs.utexas!cactus.org!cheselka (512)452-9412v ( 24hours answer. mach.)
-