> "G. Matthew Rice" <[EMAIL PROTECTED]> writes: > > I would say minimally: > > > > 1. knowledge of .bash_history > > > > how many times have you accidentally typed your password on the > > command line and then had to edit it out of the history file? I've lost > > count for myself :) > > > > 2. history command > > > > natch - it's already listed > > > > and probably: > > > > 3. !n > > > > rerunning the nth command in the history > > > > 4. !-n > > > > rerunning the nth previous command > > I think I'd like to vote for adding: > > 5. !<string> > > rerunning the previous command that started with <string> > > I had top running all night to prevent a ssh session from hanging and, after > doing some commands this morning, typed '!top' without even thinking. > > No comments from anyone on this (even Anselm and he brought it up ;)). > > Does anyone think that this is far enough (I actually prefer #5 over #3 and > #4 for LPIC-1)? > > Your last chance to say something is coming up because I have to write this up > for the addendum. Hopefully, everyone's finished their <insert favourite > winter holiday> shopping by now :) > > Regards, > --matt
Frankly, I hardly ever use the above history commands. If I can't find what I want using ctrl-r, or a few presses of the up arrow, I'm out of luck. I think the impact of readline on history editing is more important today, than the original set of arcane commands that mattered more when you were using a slow dialup line. Editing history in vi or emacs mode beats remembering another set of obscure commands. My two cents worth. Ian Shields Ph.D. Linux Technologist, ISV & Developer Relations IBM Corp Research Triangle Park, NC [EMAIL PROTECTED]
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
