<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>saagarjha</author><text>This is zsh specific, but here&amp;#x27;s something I&amp;#x27;ve been burned by enough times that I specifically wanted to mention it: save your history in a file other than the default one. Why? Because if you increase the history limit, and your profile isn&amp;#x27;t sourced for any reason, the shell will read your history file and use the default history size, clobbering everything that&amp;#x27;s there. If you use a non-default history file this rogue shell (missing your settings) will dump its history into the default file and leave your custom file untouched.</text><parent_chain></parent_chain></comment><story><title>Fixing macOS Zsh Terminal History Settings</title><url>https://blog.akatz.org/fixing-macos-zsh-terminal-history-settings/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>matthberg</author><text>I often have multiple concurrent sessions of terminal open, which leads to messed up history interactions. One solution I&amp;#x27;ve encountered (but have not tested yet) is zsh-histdb [0]. It stores sessions&amp;#x27; history to a SQLite db instead of a single appended file, with extra metadata about when commands were run, what session, etc. If you&amp;#x27;ve already got your .zshrc file open to mess with the history settings it might be worth checking out that tool while you&amp;#x27;re at it.&lt;p&gt;0: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;larkery&amp;#x2F;zsh-histdb&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;larkery&amp;#x2F;zsh-histdb&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Fixing macOS Zsh Terminal History Settings</title><url>https://blog.akatz.org/fixing-macos-zsh-terminal-history-settings/</url></story>