2006/2/7, Egon Kocjan <[EMAIL PROTECTED]>:
> Hi,
>
> I am having a problem with fish, since it does not always save cmdline
> history. If I press ^D, the history is saved. But if I close the terminal
> window, history is not saved. Shouldn't fish save history in this case?
It should, definitely. In theory, this should be as simple as adding
the following shellscript:
function --on-signal HUP hup_handler
exit
end
but something is going wrong, and the above seems to lock fish in a
100% CPU loop instead. I don't understand why that is happening, but
I'm guessing it has something to do with reading from file descriptors
that have been closed, getting ttin-signals as a result, etc.
>
> btw.: I'm testing 1.20.2 and prompt lag seems to be gone on suse! I'll see
> about prev/next-history bindings (incredibly slow in 1.20.1) later on.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Fish-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fish-users
>
--
Axel
