This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-15
Channels
- # announcements (1)
- # babashka (1)
- # beginners (43)
- # cider (2)
- # clj-kondo (29)
- # clojure (61)
- # clojure-austin (18)
- # clojure-dev (7)
- # clojure-europe (30)
- # clojure-nl (1)
- # clojure-norway (23)
- # clojure-uk (5)
- # clojuredesign-podcast (8)
- # cloverage (1)
- # conjure (1)
- # data-science (1)
- # datahike (36)
- # datavis (1)
- # datomic (23)
- # emacs (14)
- # hyperfiddle (28)
- # lsp (5)
- # missionary (1)
- # music (1)
- # off-topic (11)
- # re-frame (11)
- # reitit (5)
- # releases (1)
- # shadow-cljs (65)
- # spacemacs (13)
- # squint (33)
- # tools-deps (56)
One slight annoyance:
I'm in a rich comment block and I want to slurp the random-uuid
call. cursor indicated by |
(comment
(str |)(random-uuid)
,,,)
So, SPC k s
and it becomes this:
(comment
(str (random-uuid)))
Still fine, I can eval ok and everything but is there a way to disable this?I always put an "\n" at the end of the comment form like this:
(comment
(str "hello") "there"
\n
)
I haven't found a rule to disable this behaviour.
I tend to use #_()
to stop the format bring up the closing comment paren.
I have a rich-comment
snippet in Practicalli Clojure LSP Config that creates the following code
(comment
#_())
A very simple approach is to add a ,
(comma) before the closing paren of the comment expression, as commas are considered whitespace by the Clojure reader
Alternatively, I've found this less of an issue when using the parinfer approach rather than paredit. Although that is a bit of a cognitive change to writing code. I've only used parinfer with Neovim so far (works well though and I am less concerned with paren wrangling)
I realized I can get lost in emacs for hours fixated on how to automate some trivial thing π
In my first year with Spacemacs I did spend quite a bit of time just submitting PRs to Spacemacs and extending my own user config. I dread to think how long it would have taken if I had tried doing this from scratch. I would certainly be using far fewer features, even nearly a decade later...
I went and had a look at some emacs/spacemacs use videos including one of yours. I think I'll gradually ease into it. For now, I am so happy with magit, magit todos, cider integration and portal. I have few kbds memorized but if I go crazy on spacemacs and your config I think I'll burn out. π
Magic Forge is great too, if using GitHub for issues and PRs (which can be created & updated in Emacs)