Curt Lundgren wrote:
If you do "!se" you'll execute the most recent command that starts
with the letters "se". I find I use this more than re-executing by
number.
Curt
I use this one quite often but it can be the source of problems if the
last command you typed beginning with that text was something that you
weren't expecting. typing !my to bring up the last mysql command line
session and catching "mysql
<production_database_install_from_two_years_ago.sql" can be upsetting.
One that is handy to know is the replace character. Handy for typos and
other things besides.
$ ls /home/user/files/long_firectory_path_to/install_files/config/blah
ls: /home/user/files/long_firectory_path_to/install_files/config/blah:
No such file or directory
$ ^f^b
ls: /home/user/files/long_directory_path_to/install_files/config/blah
file1 file2
$
(Not necessarily a good example as you'll probably use path completion
but you get the idea)
Rich
--
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en