This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-31
Channels
- # announcements (5)
- # babashka (105)
- # beginners (92)
- # calva (77)
- # cider (17)
- # cljdoc (8)
- # cljs-dev (8)
- # cljsrn (8)
- # clojure (272)
- # clojure-dev (25)
- # clojure-europe (5)
- # clojure-italy (6)
- # clojure-nl (7)
- # clojure-norway (3)
- # clojure-uk (108)
- # clojurescript (326)
- # code-reviews (4)
- # cursive (6)
- # datomic (37)
- # duct (5)
- # emacs (14)
- # fulcro (23)
- # graphql (1)
- # juxt (1)
- # kaocha (2)
- # leiningen (10)
- # malli (9)
- # music (1)
- # nrepl (12)
- # pathom (21)
- # pedestal (2)
- # planck (4)
- # quil (3)
- # reitit (29)
- # rewrite-clj (10)
- # shadow-cljs (82)
- # spacemacs (29)
- # sql (6)
- # tools-deps (19)
A question for the emacs gurus, why is it that forward-sexp
is different in grep buffer vs. e.g. clojure-mode
buffer? Former does not go over question mark in foobar?
and latter does.
I see that C-M-<right>
is bound to forward-sexp
in all the cases, I wonder how it ends up doing a different thing. I can see in clojure-mode.el
the function that does a different thing but I can't see where forward-sexp-function
is defined to be different
clojure-mode.el
is careful to use the original forward-sexp
in its implementation and sets forward-sexp-function
as nil
. Is that only for safety and the real difference is actually in the syntax table?
It's easy to jump to definition of forward-sexp
but seems that e.g. xref-find-references
doesn't find any. Google and GitHub search were most useful in this. I wonder if there is any "Emacs, please search every module you know for any reference of this"