On Thu, Jan 21, 2016 at 09:29:01AM +0100, Silvan Jegen wrote:
> On Thu, Jan 21, 2016 at 9:11 AM, Silvan Jegen <s.jegen_AT_gmail.com> wrote:
> > I came up with only two general approaches. Either send error messages
> > to the UI (including a sleep() so that errors further down in the call
> > chain don't get eclipsed) or log them to a file (both approaches feel like
> > bad choices). I wonder how other TUI programs handle their error messages.
>
> If we get rid of my assumption that we can only show one line of error
> messages in the UI we could just write all errors into some kind of
> "error buffer" and then display an "error stack" that way (without
> having to resort to sleep()).
Yes using a dedicated error file/window is the obvious way to do it.
I implemented that in one of the last commits. A syntax error or failure
to load a module from visrc.lua should no longer go unnoticed but instead
print a stack trace.
--
Marc André Tanner >< http://www.brain-dump.org/ >< GPG key: 10C93617
Received on Sun Jan 31 2016 - 11:07:13 CET