tynor@prism.gatech.EDU (TYNOR,STEPHEN D.) (09/15/89)
In the spirit of recent postings suggesting that certain items be left
off the history stack (via string length or pattern match), I'd like
to suggest that a line not be pushed onto the stack if it is identical
to the previous command (this makes ^R, ^S searches more reasonable).
Since this would not be consistent with csh (how about ksh?) history,
I 'spose a variable to enable this feature would be in order.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Progress means replacing something wrong with something more subtly wrong.
Steve Tynor
Georgia Tech Research Institute
Artificial Intelligence Branch
tynor@prism.gatech.edujjd@ALEXANDER.BBN.COM (James J Dempsey) (09/15/89)
>> From: "TYNOR,STEPHEN D." <prism!tynor@gatech.edu> >> In the spirit of recent postings suggesting that certain items be left >> off the history stack (via string length or pattern match), I'd like >> to suggest that a line not be pushed onto the stack if it is identical >> to the previous command (this makes ^R, ^S searches more reasonable). I think this is an excellent idea. The Symbolics command processor uses this approach and I like it a lot. If you do 10 "ps" commands in a row you don't have to ^P 10 times to get to the command before that. --Jim Dempsey-- BBN Communications jjd@bbn.com (ARPA Internet) ..!{decvax, harvard, wjh12, linus}!bbn!jjd
D. Allen [CGL]) (09/18/89)
I once wrote a shell that didn't put a command in the history if the command line started with a blank. Thus, my shell didn't need to keep any arbitrary list of non-history-able commands. -- -IAN! (Ian! D. Allen) idallen@watcgl.uwaterloo.ca idallen@watcgl.waterloo.edu 129.97.128.64 Computer Graphics Lab/University of Waterloo/Ontario/Canada