Peter Strömberg

Calva doesn't really have an AST. It's an array of tokens. I see no way to go from the TokenCursor to a zipper like that, even though from an API...

This is actually mostly implemented since long. Bound to `ctrl+alt+o o` by default. But VS Code's API makes it impossible to implement the reverse (from REPL window to the file)...

Thanks for reporting! I can reproduce this bug. **Before**: ```clojure a| b c ``` Calva: Kill/Delete Sexp Backwards **Expected**: ```clojure | b c ``` **Result**: ```clojure b c| ``` It...

I was wrong about `paredit.killSexpForward`. It seems to work. I'm guessing it's about the range passed to `killRange`. Struggling a bit with how to expose this in unit test...

Hmmm, these tests pass: ```typescript describe('killRange', () => { it('Deletes top-level range with backward direction', async () => { const a = docFromTextNotation('a ||b |>|c'); const b = docFromTextNotation('a |c');...

This actually has nothing to do with `killRange`. It happens when formatting the current range while at the top level: **Before**: ```clojure a | c ``` Calva: Kill/Delete Sexp Backwards...

After some more digging, it seems to be a regression upstream in VS Code. It also seems fixed in VS Code Insiders, bringing hope that it will be fixed in...

Thanks! I should of course have thought about those logs. As I don't know where this log turns uninteresting I'll paste it in full: ``` [Trace - 3:51:21 PM] Sending...

Maybe ... VS Code seems to first create an empty file and then save the text to it. clojure-lsp adds an ns and also does clean-ns is performed while the...

I started the logs, then clicked the unnamed file, and saved it. Not sure what I could do different. What is the initial request?