Peter Strömberg
Peter Strömberg
> Emacs prints the errors in its echo buffer but it's quite succinct and don't need user input to dismiss it. Yes, something like that I think Calva should do...
I can't find a way to intercept the error dialog. I asked about it here: * https://github.com/microsoft/vscode-discussions/discussions/579
> @PEZ I don't think this is happening with `textDocument/publishDiagnostics`. You're quite right. I realized my error here yesterday when trying to figure out some way to intercept this popup....
Indeed. It's being fixed there. But Calva users need to be protected from the spam of this category of errors.
What's your setting for `calva.paredit.hijackVSCodeDefaults`? If it's enabled then the `!config.calva.paredit.hijackVSCodeDefaults` would disable the shortcut. But you don't need to involve that setting in your keybinding anyway. It's more a...
It could also be that the log file has grown beyond 50Mb and we fail to catch the error from VS Code refusing to open it.
Indeed. Command-clicking the path will open it in VS Code, and probably display a proper error message.
Hi! Thanks for the report, and for the details. I can't say I understand what's going on, but it all looks eerly similar to this issue reported earlier today/yesterday: *...
It could be that the error message gets lost because it's being directed to the repl client which disconnects on the error. Pure speculation here, but you could try to...
Thanks! From the messages we do get it seems the error occurs in the nrepl server. Maybe there's a way to get it to be more verbose... There are also...