This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-13
Channels
- # aleph (15)
- # announcements (4)
- # babashka (36)
- # babashka-sci-dev (1)
- # beginners (15)
- # biff (2)
- # calva (15)
- # cider (3)
- # clj-kondo (8)
- # clojure (149)
- # clojure-europe (14)
- # clojure-norway (13)
- # clojure-switzerland (1)
- # clojure-uk (1)
- # clojurescript (21)
- # community-development (5)
- # cursive (20)
- # data-science (2)
- # datomic (7)
- # duct (5)
- # emacs (19)
- # etaoin (3)
- # events (2)
- # fulcro (11)
- # introduce-yourself (2)
- # jobs (4)
- # jobs-discuss (19)
- # joyride (1)
- # leiningen (11)
- # malli (7)
- # membrane (131)
- # nbb (12)
- # nginx (1)
- # off-topic (33)
- # pathom (8)
- # polylith (28)
- # re-frame (8)
- # sci (7)
- # shadow-cljs (225)
- # spacemacs (10)
- # specter (1)
- # vim (10)
- # xtdb (8)
A little bit annoying part when using calva comment is the indentation is mismatched.
Pictures shows before inserting comment with editor.action.commentLine and after.
Interesting. Calva is not providing this feature, iirc, so probably something to bring to the VS Code team.
On an empty line, I type one or more semicolons. I find it a bit strange that the command doesn't retain the indentation, though. I wonder why that is.
I don’t manually type the simicolons. I am used to the alt+; key shortcut in emacs to insert comments.
Can I set the line width to the current editor width? https://calva.io/pprint/#:~:text=function%2C%20more%20below.-,width,-number
Would it be possible to have Calva play nice with git extension, when I evaluate the results are shown after the git info. See: On my screen that means the results are often entirely off the screen (I code on a vertical monitor). Or anyone got any workarounds / configs ?
Hmm that doesn’t happen for me, but I feel like I’ve seen this discussed before. Any info @U0ETXRFEW?
We've discussed it before. GitLens is using the :after selector for the line blames. Calva used to use :before for this reason, but it pushed the cursor away to the end of the displayed result. https://github.com/BetterThanTomorrow/calva/issues/1329 Using the same selector as GitLens means it comes down to which extension is first to decorate the line. We could consider making this a setting, as we discussed before fixing #1329.
Thanks for all the incredible work being done on Calva. Recently I’m having a problem whenever I delete a top-level form using ctrl+alt+backspace. The form is correctly deleted, but also the cursor jumps to the end of the file. How can I debug what’s going here?
Hi! To my surprise, I can reproduce this. At the top level of the file. Please file an issue. If you want to help debug it, that would be awesome. I think it takes running Calva in dev mode and place breakpoints in the right places in paredit.ts. See https://github.com/BetterThanTomorrow/calva/wiki/How-to-Hack-on-Calva for how to get dev Calva running, if you haven't before. If you don't have time for debugging like that, just an issue is good help that too. I'll be afk for a some days probably so will have a look later if someone else doesn't beat me to it.
Perhaps related: sometimes when I inline evaluate expressions and the result is rather long, it jumps far right in the editor. This is expected. After that when I evaluate an expression and the result is short, cursor still jumps to the end of the file where I just landed with the long result.
Filed an issue: https://github.com/BetterThanTomorrow/calva/issues/1801. I will try to look further into it as well and add more comments to the issue if I find anything relevant
It seems to be a regression in VS Code, and it also seems to be fixed in VS Code Insiders, so there's hope. I fail to find a relevant issue on VS Code, and asked about that here: https://github.com/microsoft/vscode-discussions/discussions/67