Fish sessions synchronize their history periodically (every 5 mins by
default IIRC) to a global settings daemon. So you probably will not be able
to avoid history pollution in this case by killing the session.
Havind said that, `kill -9 %self` should do what you want.
Steve Stagg
On Jul 8, 2009 8:49am, Radu Benea <[email protected]> wrote:
Hi,
I've been a bash user for quite a while and whenever I don't want history
saved for the current terminal I'm used to killing it with
kill -9 0
which in bash terminates the process kill was started from
also tries kill -9 $$ - without luck
but in fish it attempts to kill 1 (which is init)
any suggestions?
------------------------------------------------------------------------------
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
------------------------------------------------------------------------------
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
