Sky Higgins

> and only if clojure-lsp is not serving Not sure what you mean by this. Even with LSP running, a keyword gets recolored to look like a symbol.

Hmmm. That is different from the behavior on my system. Clojure LSP serving does not fix the issue like your screenshot shows.

Verified what you described, that semantic tokens override the Textmate grammar with the correct Reader interpretation. My theme for some reason disables it on my behalf if `editor.semanticHighlighting.enabled` is set...

This issue explains why Buffer is unsafe. https://github.com/nodejs/node/issues/4660 And the deprecating commit. https://github.com/nodejs/node-eps/pull/4 Seems we are at fairly low risk, since not providing an http service, but I expect we...

After eliminating markdown files, and files that were clearly tests or examples (based on path and/or file name), I found occurrences of `Buffer(...)` or `new Buffer(...)` in the following files...

Since it has been a couple weeks without progress, I think it is worth an explicit answer here that I do intend to work on this.

Understand your reasoning. Would you consider a PR, or is this just dead in the water?

I am getting intermittent results on that particular reduction of the problem as well. Typing into `({|})` will throw 100%. With only ({}), we get a lint error but otherwise...

It seems Calva never has its hands directly on the event flow that leads to this bug. We tell clojure-lsp to handle `codeActions` when initializing the server, and then Code...

Here is a partial workaround until this can be solved: Adding this to your `keybindings.json` provides a `Shift+Esc` shortcut to dismiss all notifications, whenever any are visible, regardless of focus....