@AndreasArvidsson had this idea during a community meeting, and I thought it was quite a captivating one.
Talon currently prints a decent number of warnings to the log (invalid symbols in lists, Talonfile parsing errors, use of deprecated functions, etc), but it can be easy to miss them. And, when you're in the mood to fix things, it can be difficult to ascertain how close you are to an ideal state without digging through your own log. I usually restart Talon to see if I have any errors that will trigger on startup but this is not ideal.
It would be cool if, in the same vein as the new Rust debug windows, there could be some version of the "problems list" window you can get in VS Code. Specifically, the one that you get with TypeScript, which reliably live updates as you change files.
I imagine this kind of tracking is nontrivial to do, but would be very handy, especially when diagnosing problems with new users.
@AndreasArvidsson had this idea during a community meeting, and I thought it was quite a captivating one.
Talon currently prints a decent number of warnings to the log (invalid symbols in lists, Talonfile parsing errors, use of deprecated functions, etc), but it can be easy to miss them. And, when you're in the mood to fix things, it can be difficult to ascertain how close you are to an ideal state without digging through your own log. I usually restart Talon to see if I have any errors that will trigger on startup but this is not ideal.
It would be cool if, in the same vein as the new Rust debug windows, there could be some version of the "problems list" window you can get in VS Code. Specifically, the one that you get with TypeScript, which reliably live updates as you change files.
I imagine this kind of tracking is nontrivial to do, but would be very handy, especially when diagnosing problems with new users.