Hi Anselm,
This is something that we can add to the clarifications on Jan 1st.
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'll leave the rest up to others to help with the clarification.
I think what you showed below is sick ;)
I'm even on the fence with my old favourite: ^ (the quick sub character)
Also, I don't think we need to add (not really history specific) the
emacs/vi/etc keybindings for editting on the command line.
Comments? Additional really useful history related topics?
Remember, this is junior level and history is just one part of the 4
weight objective.
Regards,
--matt
On Fri, 2008-12-05 at 15:31 +0100, Anselm Lingnau wrote:
> Here's one that makes me wonder: How far does »Use and edit command history«
> in the new-style objective 103.1 extend into the territory of arcane history
> substitutions, i.e., do LPIC-1 candidates have to be able to parse and/or
> produce things like
>
> $ echo !?foo?$:t:s/bar/baz/
>
> ? If not, where does objective 103.1 stop?
>
> (Just in case you're wondering: This will look for the most recent command
> line in the history containing the string »foo«, pick up the last word of
> that line, discard everything from that word except for the last filename
> component, and return that with the string »bar« replaced by »baz«. And just
> for the record, I don't use such things myself as my poor brain cannot handle
> them as a matter of course.)
>
> Anselm
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
