Re: MinGW version binary gobbledygook error messages?

[Sebastien Loisel]

1) The error messages are goobledegook sometimes in MinGW. Once they
change to goobledegook they stay that way. Ideas?

I'll keep my eyes peeled for it and indeed it will need to be fixed at some point, but it's not so easy for me to debug. My struggles with command_editor are much more pressing (and might I add, unanswered!)

You've pointed out to me several times that eval_string() isn't the right way of doing things. I've been wanting to change to command_editor, but the class is large and I don't understand it. Where do I start?

Sébastien Loisel