Hi, http://blog.macromates.com/2008/working-with-history-in-bash/ I knew how to get your history file to remember all your previous commands, but saving and appending from all closing bash shells, I hadn't found yet. :) -Kenny -- ================================================================== Kenny Billiau Web Developer Tel:+32 (0)9 331 36 95 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM kenny.billiau@psb.ugent.be http://bioinformatics.psb.ugent.be ==================================================================
Kenny Billiau schreef:
http://blog.macromates.com/2008/working-with-history-in-bash/
I knew how to get your history file to remember all your previous commands, but saving and appending from all closing bash shells, I hadn't found yet. :)
I don't quite understand the default policy of history either. Sometimes, your commands are saved, but indeed when working with multiple shells, you tend to lose some sessions completely while keeping others. Btw, I have this one in my .bashrc as well: export HISTTIMEFORMAT="%F (%H:%M) : " It gives your history entries a nice timestamp. T. PS. didn't know the nodups option either, but it rocks :-) -- ================================================================== Thomas Van Parys Tel:+32 (0)9 331 36 95 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM thomas.vanparys@psb.ugent.be http://bioinformatics.psb.ugent.be ==================================================================
Do you know if the HISTTIMEFORMAT messes up the nodups option or the recursive search function? I can't live without the rec search ;) -Kenny On Wed, 10 Sep 2008, Thomas Van Parys wrote:
Kenny Billiau schreef:
http://blog.macromates.com/2008/working-with-history-in-bash/
I knew how to get your history file to remember all your previous commands, but saving and appending from all closing bash shells, I hadn't found yet. :)
I don't quite understand the default policy of history either. Sometimes, your commands are saved, but indeed when working with multiple shells, you tend to lose some sessions completely while keeping others.
Btw, I have this one in my .bashrc as well: export HISTTIMEFORMAT="%F (%H:%M) : "
It gives your history entries a nice timestamp.
T.
PS. didn't know the nodups option either, but it rocks :-)
--
Kenny Billiau schreef:
Do you know if the HISTTIMEFORMAT messes up the nodups option or the recursive search function?
The timestamps are ignored when deleting duplicates.
I can't live without the rec search ;)
I felt the same about WoW. Just try a day without it. T.
On Wed, 10 Sep 2008, Thomas Van Parys wrote:
Kenny Billiau schreef:
http://blog.macromates.com/2008/working-with-history-in-bash/
I knew how to get your history file to remember all your previous commands, but saving and appending from all closing bash shells, I hadn't found yet. :)
I don't quite understand the default policy of history either. Sometimes, your commands are saved, but indeed when working with multiple shells, you tend to lose some sessions completely while keeping others.
Btw, I have this one in my .bashrc as well: export HISTTIMEFORMAT="%F (%H:%M) : "
It gives your history entries a nice timestamp.
T.
PS. didn't know the nodups option either, but it rocks :-)
-- ================================================================== Thomas Van Parys Tel:+32 (0)9 331 36 95 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM thomas.vanparys@psb.ugent.be http://bioinformatics.psb.ugent.be ==================================================================
participants (2)
-
Kenny Billiau -
Thomas Van Parys