> If you could give a more precise description of the problem, we could
> probably find a better "fix".
> E.g. show us a backtrace,
> I don't have one. As I said, I was experimenting, and I must have somehow
> stuck a string onto the command history (I don't remember the details). Yes,
> history lists are internal data, and shouldn't get corrupted unless you play
> around like I did. So there is no real requirement to worry about this.
> My point was simply to add something simple, to catch a malformed history
> list, should one arise. I wasn't really asking that measures be taken to
> ensure that histories are never malformed or to fix malformed histories.
The better fix wouldn't be to prevent malformed histories but to catch the
problem closer to its source so as not to ignore other errors.
Stefan
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
