Johannes Schauer Marin Rodrigues <jo...@debian.org> writes: > The problem with ridiculously long error messages is, that mmdebstrap > currently has no way to wrap long error messages after 80 columns or > so. A very long error message is hard to read if it doesn't get > wrapped similar to how you did it in your example.
I don't think this is something that mmdebstrap should be thinking about. Error messages aren't something that needs to be immediately fully consumable at a glance. Debugging takes time, and if we can save the user even a bit of debugging time, then the extra minute it takes for them to wrap the line is worth it. And does it really take any time at all? I use either xterm or the emacs shell 100% of the time, and both of those will wrap long lines to make them legible, without me having to ask. > The second reason is, that it would not be easy to store and forward > the reason why the other modes failed. Especially the unshare mode can > fail for 26 different reasons if I counted correctly. Letting the > test-function silently fail when checking for the mode but extracting > the error message would turn the code even more into spagetti. Yeah. I was wondering if this was the case. I think what you have is great. Ship it! And thanks.
