on a mac, ctrl-right doesn’t seem to move forward a sexp. I’ve checked to see if there are any other shortcuts on it, doesn’t seem to be…wonder what the problem is
Obviously it can be changed, but I am setting this up for a bunch of interns, so I’d rather get defaults working
Wow. Alt right works. Didn’t realise both were mapped to the same fn
They shouldn’t be. alt
should be, ctrl
should not.
I don’t know why VS Code displays it like that. There’s an issue about it. But anyway, ctrl +up/down is not navigating sexpr on Mac.
Cool, thanks
Keyboard -> Shortcuts -> Mission Control
I’ve got that disabled. The problem here isn’t that it is doing something else. The problem seems to be that VSCode lists both ctrl right and alt right as keyboard options
I think it is this issue. Which we haven’t investigated enough upstream: https://github.com/BetterThanTomorrow/calva/issues/1161
Hey - is there any workaround for [2021-05-12 23:04:52.365] [exthost] [error] Namespaced keywords not supported ! calva-fmt.formatCurrentForm
or you can’t plainly do any formatting of code with ::foo
with calva-fmt
?
There is no workaround yet. We need to upgrade our fork of cljfmt
.
Hi all, any tips on best practices for writing docstrings for nice rendering in Calva? Also on that note, wondering if it’s possible to render markdown somehow on hover?
@slawek098 @pez Created an issue for updating our cljfmt here: https://github.com/BetterThanTomorrow/calva/issues/1179 Didn't see an existing one.
The hovers do render markdown, but there are two sides to this. When a repl is not connected, the hover content comes from clojure-lsp. When the repl is connected, hover content comes from nrepl and I think is packaged/formatted by Calva. 1. When the repl is not connected, clojure-lsp sends the hover response like the below. @ericdallo Do you think it would be okay to not enclose the doc string in a clojure code block? I think this would allow the markdown the user sets in the doc string to be respected in the hover.
"contents": {
"kind": "markdown",
"value": "
clojure\ncore/one\n\n
clojure\n[x]\n\n\n----\n
clojure\n*hello world*\n\n----\n*/home/brandon/development/clojure-test/src/core.clj*"
}
2. When the repl is connected, hovers are formatted with this code here: https://github.com/BetterThanTomorrow/calva/blob/a1afb5799bc8f1e4063badb8964f462b1da7dfcc/src/providers/infoparser.ts#L168. I haven't examined it closely but I'm guessing something there prevents user-defined markup from being respected. @pez is there a reason for this?I didn't get the idea @brandon.ringe :thinking-face:
Currently in a doc string if I set it to "*hello world*"
it should render as bold in the hover (in my opinion, at least). But clojure-lsp sends the doc string content back wrapped in a clojure code block (
clojure\n*hello world*\n
), so it renders it as code instead of making it bold.Is there a reason for that? I would like it to not render as Clojure code, because it will highlight Clojure function names like if
even when it's not meant to be code. Like so: