This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-21
Channels
- # announcements (12)
- # aws (1)
- # babashka (82)
- # beginners (89)
- # calva (8)
- # cider (20)
- # clj-kondo (1)
- # clojars (9)
- # clojure (120)
- # clojure-australia (3)
- # clojure-europe (14)
- # clojure-france (24)
- # clojure-germany (3)
- # clojure-italy (16)
- # clojure-nl (1)
- # clojure-spec (3)
- # clojure-uk (22)
- # clojurescript (26)
- # cursive (38)
- # datascript (1)
- # emacs (10)
- # events (1)
- # helix (7)
- # jackdaw (5)
- # jobs-discuss (37)
- # lambdaisland (10)
- # malli (20)
- # meander (2)
- # off-topic (15)
- # pathom (42)
- # quil (1)
- # re-frame (38)
- # react (2)
- # reitit (2)
- # reveal (9)
- # rewrite-clj (3)
- # ring (5)
- # shadow-cljs (84)
- # spacemacs (1)
- # tools-deps (23)
- # vim (8)
- # vscode (1)
I’m trying to create a command that reloads the buffer, evaluates it and then evaluates a specific mark (using #conjure)
nnoremap <Leader>x :edit <CR> <localleader>eb
It looks like the <localleader>eb
thing isn’t triggered, anyone have a pointer why that is?I did try that but didn’t see any indication that the \eb
was actually run
You might want to try nmap
instead of nnoremap
.
I think the difference is that nmap
is like pressing those keys verbatim, which takes into account things like plugins you have installed and other mappings that you've created.
Whereas nnoremap
is like pressing those keys on a fresh vim install with no config. Or something to that effect.
In general, nnoremap
is preferable, but in this case, I think you probably want nmap
because <localleader>eb
means something specific to your config.
Didn’t understand the difference between nmap
and nnoremap
but now that you said it it makes perfect sense!