This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-31
Channels
- # announcements (4)
- # aws-lambda (1)
- # babashka (25)
- # beginners (60)
- # calva (33)
- # cider (15)
- # cljdoc (1)
- # clojure (28)
- # clojure-dev (1)
- # clojure-europe (4)
- # clojurescript (29)
- # clojureverse-ops (4)
- # conjure (10)
- # datomic (4)
- # graalvm (4)
- # holy-lambda (4)
- # honeysql (13)
- # introduce-yourself (1)
- # lambdaisland (1)
- # missionary (11)
- # music (2)
- # off-topic (35)
- # pathom (17)
- # pedestal (20)
- # reagent (3)
- # sci (10)
- # shadow-cljs (39)
- # sql (6)
- # tools-deps (6)
- # vim (1)
@slawek098 im using neovim for vscode and it alwayw moves through thr whole one. I thought there are vim plugins for that but I didnt try that yet
So it definitely works sometimes. In regular vim plugin there is word boundary setting that should stop on -
https://github.com/VSCodeVim/Vim/issues/1090 for vscode-vim there seems to be the vim.iskeyword
setting but it sounds weird to me that it sometimes works and sometimes not
I’ve created an issue: https://github.com/BetterThanTomorrow/calva/issues/1246
I'd say that might be by design, or just an artifact of how vscode allows this to be handled. It's the same if you double-click foo
in foo-bar
.
Ok... very weird behavior. When any of the two (calva, vscode vim) are disabled, editor reloaded and again enabled it starts working (stopping at -
). If calva is never activated it always works.
If calva and vscode vim are both active when starting vscode it will not stop at -
and jump to the end of the word.
It's entirely possible. There can only be one definition of what is a word and if two extensions compete about it only one will succeed.
In vim (at least neovim) if you add something to iskeyword
it is treated as part of the text (respectively you will jump over it with w
)
In vscode-vim if you add something to iskeyword
the opposite happens. It is treated as word-boundary.
It is, but the naming for vim-users is quite off then.
I find it also weird that whenever you set vim.iskeyword
the editor word separator settings are instantly overwritten instead of just using the precedence. May be that it wasn't otherwise possible to implement.
That aside, I sadly could not figure out what in calva could override the word boundaries
In Calva the word pattern is defined like so: "wordPattern": "[^\\s,#()[\\]{}꞉;\"\\\\@]+"
And word separators like so:
"editor.wordSeparators": "\t ()\"':,;~@#$%^&{}[]`"
https://calva.io/customizing/#clojure-defaults👏 I don't know who to thank so I'm throwing it out here. I just find it truly amazing that I can get code completion in calva on Node dependencies out-of-the-box with shadow 🎉
Iirc, that’s a lot @robertkrahn’s doing. And of course @bozhidar. https://github.com/clojure-emacs/clj-suitable