diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-07-21 23:38:21 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-07-21 23:38:21 -0700 |
commit | 4efc0ff3168f9ff6e80b2fa4b3302baac4035abb (patch) | |
tree | 83843682dfa136f08f7a3603902d39f8b76c10b5 /display.mu | |
parent | efc5c081304f7da0d8ffcc863f14922845d04295 (diff) | |
download | mu-4efc0ff3168f9ff6e80b2fa4b3302baac4035abb.tar.gz |
1826 - edit: start carefully showing all errors
Eventually we might be able to get rid of die entirely. This is just a preliminary stab at a random error. In the process I ran into two issues that have impeded debugging before: a) Naming conflicts within scenarios are a real no-no. I need to warn on them, but the rules are getting complicated: Always print warnings on redefine But not in interactive mode Or in scenarios checking warning behavior Unless the scenario recipe itself is overridden b) Now that we've added collect_layers and a long time can go between traces, debugging is a minefield because trace lines don't print to screen immediately after they're created. Need to do something about that. Maybe explicitly trigger collection by tracing '\n' or something. These are the next two items on my todo list.
Diffstat (limited to 'display.mu')
0 files changed, 0 insertions, 0 deletions