Under the known bugs and issues:
History file should apply some kind of maximum history length
Fine, but the default needs to be large, like 100MB. Disks are big now. I hope ridiculousfish agrees.
History file should apply some kind of maximum history length
Fine, but the default needs to be large, like 100MB. Disks are big now. I hope ridiculousfish agrees.
This bug is actually fixed with my changes (see the release notes at http://ridiculousfish.com/shell/release_notes.html). The maximum history length is now 250k unique items, with an LRU discard policy. A full history would be around 15 MB.
Processing time is one concern. fish doesn't do anything as clumsy as keeping the entire file in memory, but scanning a large history file can still add up.
But the larger concern is writing it out. fish saves its history atomically by writing an entirely new file to disk, and swapping it in. You may not notice a 100 MB file, but you would probably notice a frequent 100 MB write!
That's so you get sync'd histories across one user's logins? Good feature, but I need my history. It's invaluable to me. Still, maybe 250k lines is enough. Is there a way I could bump that up and judge for myself the consequences?
I'd be happy with 100 MB as a maximum size but there should also be time-based limits, like remove anything from history that is older than a few months.
more: http://www.linuxjournal.com/content/using-bash-history-more-...
Yes.
visible to anyone with physical access to your box
Maybe not. That's an auth problem, not a reason to throw away your archives. I keep all my email even though there's probably something in there embarrassing to me given some audience.