home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.shell
- Path: sparky!uunet!convex!news.utdallas.edu!hermes.chpc.utexas.edu!aswx266
- From: aswx266@chpc.utexas.edu (Michael Lemke)
- Subject: Re: tcsh in the future - what should it be like?
- Message-ID: <1992Jul27.031238.10376@chpc.utexas.edu>
- Keywords: tcsh
- Organization: The University of Texas System - CHPC
- References: <yeates.711122638@beryl17> <1992Jul16.153506.24366@bmerh85.bnr.ca>
- Distribution: comp.unix.shell
- Date: Mon, 27 Jul 92 03:12:38 GMT
- Lines: 30
-
- In article <1992Jul16.153506.24366@bmerh85.bnr.ca> sjane@bmers248.bnr.ca (sjs) writes:
- >In article <yeates.711122638@beryl17> yeates@rtsg.mot.com (Tony J Yeates) writes:
- >>I thought it might be interesting to make suggestions for future
- >>enhancements to tcsh.
- >>
- >>e.g. type "vi " then hit a "choosen key" (up arrow is already taken) to
- >>scroll thro'
- >>(only) the previous vi commands.
- >
- >This function is already available. It is called history-search-backward.
- >You can bind it to a function key as I have bound it to F7 on my Sun:
- >
- >bindkey ^[[230z history-search-backward
- >
- >History-search-forward is also available in case you go too far too fast
- >with history-search-backward.
-
- I'd like to see a history mechanism that works like VMS' RECALL, i.e.
- type something like !vi .cs and get the last vi command that edits
- .cshrc. Simple, powerful concept; only a single command to learn.
-
- Also, the history list should save a command only if it is different
- from the last one.
-
- If both these questions have solutions already it only shows that tcsh
- has too many features. I can't remember them so I don't use them.
- --
- Michael Lemke
- Astronomy, UT Austin, Texas
- (michael@io.as.utexas.edu or UTSPAN::UTADNX::IO::MICHAEL [SPAN])
-