Guido Berhoerster dixit: >Hmm, I've done a bit more testing, sometimes it works, sometimes >it does not
Right, it’s not reliable. All I can tell you is that they synchronise with $HISTFILE upon pressing Enter (which implies that order may be important). >use the same $HISTFILE but one seems to have gone ahead of the >other and they do not get back in sync: Line numbers are out of sync anyway. Honestly, from looking at the source, I’d rather rip out the entire source code and remove persistent history feature. It cannot ever have worked, and I was only able to plug the worst things. I cannot design something that would work properly either (unless using a separate database server to store the history lines – and even then… line numbers are per shell, even though they do appear in the history file… I don’t get the reason behind that myself, either). I’ve done what I could to fix persistent history, and then some, but, tbh, you’re in unsupported territory there. I’ll not remove it, since it “mostly” works (but once the amount of lines in $HISTFILE reaches $HISTSIZE you better increase the latter or start praying or only ever run one interactive mksh instance), but that’s it. bye, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
