This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-08
Channels
- # asami (22)
- # babashka (35)
- # beginners (4)
- # calva (76)
- # cider (7)
- # clj-on-windows (89)
- # clojure (30)
- # clojure-europe (25)
- # clojurescript (10)
- # conjure (46)
- # fulcro (13)
- # gratitude (5)
- # lambdaisland (4)
- # lsp (13)
- # malli (5)
- # membrane (6)
- # nbb (1)
- # off-topic (11)
- # re-frame (2)
- # releases (1)
- # shadow-cljs (45)
- # xtdb (4)
Can lsp be configured to jump to the definition of a symbol that comes from a dependency that has been overwritten in .clojure/deps.edn with a :local/root and not from what seems to be a cached filed that can't be edited and recompiled?
Another parsing exception, in the same general category as https://github.com/clojure-lsp/clojure-lsp/issues/1268. But this one I can reproduce at near-minimal-case with totally valid Clojure code. I guess I should just add it to the issue?
Almost any string starting with \
as first item inside parens throws, which is perfectly good code, as long is it's quoted.
'("\x") ;; 💣
'("\xyz foo bar bz" :foo :bar "baz" {} []) ;; 💣
Almost any string starting with \
as first item inside parens, which is perfectly good code, as long is it is quoted. Weirdly a few characters in place of the x
above don't throw.
`("\f") ;; okay
`("\foo") ;; okay
So far I found f
, b
, r
, and t
, do not throw, but F
, B
, R
, and T
still do.user=> "\x"
Syntax error reading source at (REPL:1:4).
Unsupported escape character: \x
🙏 1