Issue #393 wontfix

Save Error Output

Anonymous created an issue

Since the using the clipboard isn't on the table, it would seem wise to offer a different way for Lovers to get the exact text of a blue screen without having to open up a text editor and type it themselves line by line.

A possibility would be to offer saving at the end of the error message- something along the lines of

"Press S to save this message to " .. love.filesystem.getSaveDirectory() .. "/error.txt"

That way they can save the error, open it up, and get help without having to retype a lengthy error message.

Comments (4)

  1. Boolsheet

    Personally, I like the idea of the option to save the error message to a file. Perhaps to <application data directory>/love/error.log. This could conflict with some LÖVE design desicion though.

    Lovers can also already do this themselves with IO redirection or custom error handlers. The default error handler (boot.lua:682) can be replaced with a slightly modified version of itself which includes the save-to-file option.

  2. Bart van Strien

    I'm not sure why this would have to be built in, if you want this for your specific game, it's trivial to add, if you want to get error messages in general, they are printed on the console as well.

  3. Eric Gaudet

    The message on the blue screen is also printed on the console. If you start love from the command line, you can just copy and paste the stack trace.

  4. Bart van Strien

    This only increases the possibilities of errors in the error handlers, you could do this yourself in a custom error handler, and redirection can also do this. I don't see the added value.

  5. Log in to comment