Dear bash-scientists, It has been a while since I've developed my "tune-up" feature for bash: never-ending bash history. It is described in details on my webpage
http://www.onerussian.com/Linux/bash_history.phtml Me and couple more folks find it very useful to keep the bash history of all the actions logged in the file. I have some tech problems because I might not know some specifics of bash implementation which would allow me to reduce overhead of my historying and make it more stable. Issues are: 1. I can't call history from .bashrc because it is not initialized by that point. If I do "set -o history" then it reads it, but then it reads it once again somewhere during bash initialization process which screws me up. I need that to remove my nasty (buggy if anything like HISTIGNORE is used) wc on .bash_history at the beginning of the session. If I could have history read at the moment of bashrc initialization, I could just assign CURBASHSTART with HISTCMD 2. I had to forbid users from pressing Ctrl-D on exit because I couldn't attach a hook to that action. I just found .bash_logout, but that works only for login sessions. 3. There might be much simpler way to accomplish what I've done! :-) Thank you in advance for any comments or suggestions. I would greatly appreciate any input P.S. Please CC replies to me as well -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers Office (973) 353-5440 x263 Fax (973) 353-1171 Ph.D. Student CS Dept. NJIT _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
