This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-14
Channels
- # announcements (7)
- # aws (1)
- # babashka (1)
- # beginners (19)
- # calva (9)
- # clj-commons (4)
- # clj-kondo (64)
- # clj-on-windows (27)
- # cljsrn (12)
- # clojure (127)
- # clojure-bay-area (3)
- # clojure-europe (25)
- # clojure-hungary (7)
- # clojure-nl (1)
- # clojure-norway (9)
- # clojure-spec (5)
- # clojure-survey (2)
- # clojure-uk (22)
- # community-development (5)
- # core-async (19)
- # cursive (29)
- # datascript (8)
- # events (1)
- # fulcro (2)
- # graalvm (3)
- # jobs (1)
- # lsp (155)
- # malli (18)
- # nbb (6)
- # off-topic (86)
- # pathom (2)
- # rdf (18)
- # re-frame (9)
- # releases (2)
- # scittle (24)
- # shadow-cljs (33)
- # xtdb (4)
I prefer to use auto completion by typing the initial letter of each word. When calling my-very-long-variable
I like to type mvlv
. This works with the REPL connected and the def/defn
is evaluated. However, if I can have some wishful thinking, I would like for the kebab case to be listed first on the popup instead of whatever ordering it's using. In this small example the first two results would be send-off
and small-one
. I am clueless on how to achieve this, any thoughts?
I have been using "editor.suggestSelection":"recentlyUsedByPrefix"
, which helps a bit
I think these suggestions come from cider-nrepl, and probably the ordering comes from that by default too (without having looked at the Calva code). I’m not sure most people would prefer the ordering you describe, but there’s probably a way to do it in Calva after the completions are received from cider-nrepl. @U0ETXRFEW What are your thoughts?
I don't see OP as a suggestion to change the default orderin? More of a way to make it behave differently, right @U031447U0F9? In any case, I don't think the default should change, and I don't know how to make it behave in a kebab-way. ... What I do is that I type s-o
in this case.
The idea would be to change the order to show kebab matches first, this would be optional using a configuration. It's hard to get a feel if that would also works well. Because whenever I type so
for some
, some?
, sort
, etc. the behavior today works very well. With said configuration these results would appear further down and could be annoying in a lot of cases.
I guess I'll just get used to typing s-o
for small kebab words and live with that.
I think VS Code will be hard to convince to select in that way. And even so, I hesitate to make it configurable in Calva. Settings add maintenance and also cognitive load for the users.
valid points