Closed olafurpg closed 5 years ago
I think that's doable by passing a loglevel as an option to the server and configuring the vscode launcher to pass the option when launched in debug mode.
By the way, from the LSP point of view all messages are logged with the "debug" level:
I think they should use info/warn/error/log levels. In Atom they currently all look the same:
But sbt messages look different, because they set this level properly (except for those "Done"/"Processing", which are a whole different story):
wdyt about configuring the minimum debug level according to a configuration option?
big +1 on this, it would also be useful for the vscode client, which has different run configurations (debug/"prod") already.
All log entries have been removed in #292, we can restart this discussion in case the new implementation emits noisy logs. I will do my best to keep the noise down
.metals/metals.log
emits a lot of noisy logsWe should clean up the logs so that they are easier to read. I'm wondering if we can figure out a way to override the default log level so that we can get extra verbose output when debugging. Any ideas?