According to multiplexd this is likely fixed in R56. If not, pleas e
open a new issue.
** Changed in: mksh
Status: New => Fix Released
--
You received this bug notification because you are a member of mksh
Mailing List, which is subscribed to mksh.
Matching subscriptions: mkshlist-to-mksh-bugmail
https://bugs.launchpad.net/bugs/1694943
Title:
history from one of many parallel shell sessions sometimes not stored
Status in mksh:
Fix Released
Bug description:
Natureshadow reports that, when having multiple parallel mksh sessions
that share the same HISTFILE, after exiting one of them and then
starting a new one, the history from the shell just terminated is not
available.
We currently believe this is due to history truncation (i.e. number of
history lines approaching $HISTSIZE). There are known issues with the
code (which is another reason HISTFILE is unset by default, and
persistent history support so -><- close to having been removed). A
workaround is:
① make HISTSIZE bigger
② truncate manually by setting HISTSIZE small while only one shell is
accessing the HISTFILE
Ideally we’d have a PostgreSQL history backend, but that won’t work
for obvious reasons. I’m not sure how much we can do with the current
ⓐ history file format and ⓑ command line editing code, but
improvements are planned for libmkshedit when at least the latter is
going to be redesigned anyway and the former can change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mksh/+bug/1694943/+subscriptions
