Separate Yash histories for separate shell instances?
by Turbocapitalist from LinuxQuestions.org on (#6Q2V8)
I have been moving more away from Bash and Zsh to Yash for some accounts lately.
When I run multiple instances of Yash on one system, these instances all share a single history file. Thus, all the shells use the same history data in the same order. I'm not sure if that is a feature or a misfeature. The benefit is that commands which have been executed by a shell instance can be recalled on another shell instance. A really big disadvantage is that I cannot keep separate activities distinct.
So if I have one window with activity A and another window with activity B and a third with activity C, there is trouble. If I switch between them at long intervals, say from A to B to C and back to A again after some hours. The original commands from activity A are now way back in the history and I cannot easily get to them, having to roll past the work in C and then B first.
How can I turn off the shared history in Yash such that each session keeps its own history, at least until the session is closed. It's fine if the histories merge upon closure.
When I run multiple instances of Yash on one system, these instances all share a single history file. Thus, all the shells use the same history data in the same order. I'm not sure if that is a feature or a misfeature. The benefit is that commands which have been executed by a shell instance can be recalled on another shell instance. A really big disadvantage is that I cannot keep separate activities distinct.
So if I have one window with activity A and another window with activity B and a third with activity C, there is trouble. If I switch between them at long intervals, say from A to B to C and back to A again after some hours. The original commands from activity A are now way back in the history and I cannot easily get to them, having to roll past the work in C and then B first.
How can I turn off the shared history in Yash such that each session keeps its own history, at least until the session is closed. It's fine if the histories merge upon closure.