This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # 100-days-of-code (8)
- # announcements (4)
- # beginners (77)
- # boot (11)
- # business (13)
- # cider (69)
- # clara (2)
- # cljdoc (51)
- # clojure (59)
- # clojure-dev (18)
- # clojure-italy (4)
- # clojure-nl (11)
- # clojure-spec (54)
- # clojure-uk (115)
- # clojurescript (33)
- # core-async (4)
- # cursive (95)
- # datomic (27)
- # duct (1)
- # emacs (58)
- # figwheel (22)
- # figwheel-main (63)
- # garden (1)
- # graphql (10)
- # hyperfiddle (1)
- # leiningen (1)
- # luminus (6)
- # off-topic (12)
- # planck (7)
- # portkey (1)
- # quil (3)
- # re-frame (3)
- # reagent (5)
- # ring-swagger (3)
- # shadow-cljs (34)
- # slack-help (19)
- # spacemacs (57)
- # testing (2)
- # timbre (2)
- # tools-deps (42)
- # yada (6)
Thanks @chase-lambert! I love Vim keybindings when moving around code, since they are objectively more ergonomical. But I am now learning the pure Emacs way, I have a hunch it’s a better fit for Lispy stuff. Plus yes, all the guides out there really are made for the default keybindings.
I can agree with this. One thing I started doing with Vim (and I was never a huge power user) and now with Emacs keybindings is using search to navigate as quickly and efficiently as possible.
C-s really gets me somewhere pretty fast and I still have a lot to learn in terms of navigating in such a manner. Something to think about if you aren't already doing so.
@U7PBP4UVA I have made the transition the other way, from Emacs to Vim bindings. As a long term Emacs user, I find Vim keybindings so much faster and easier to type. I use Spacemacs as my base configuration, as it provides Vim bindings for all modes. There is also lisp state which is great for structural editing of lisp code.
> he’s just kept pushing the 2.1 release out so now “develop” is ~3k+ commits ahead of the last release
Well, I think Prelude doesn’t have so many commits for its entire existence. 😄 I wonder what those people are doing - that’s just an Emacs config after all. 😄 😄 😄
As a comparison - my personal config has just 71 commits (https://github.com/bbatsov/emacs.d)
It used to be my own configuration for a long period of time, but then I got annoyed that I had to add a lot of flexibility there, which I didn’t really need myself, as I know exactly what I want to use. It also became harder to make baseline changes, as I had to think about impacting the users. At this point I decided that Prelude and my config become separate things. 🙂
In general I think that most Clojure devs need simply a 100-lines of config with 5-10 packages in it and they’ll be fine.
Yeah, that’s the direction I’m going for. For JS stuff I’ve resigned myself to VSCode these days.
Vs code has some pretty nice static analysis which is very useful when exploring a codebase.
Which is I think something of a divide between tools. Modern IDEs seem to target exploration, old editors creation. Perhaps I’m just making things up though :)
I have to say I somewhat agree with it - I recall I was thinking along the same lines when I made the switch from IDEs to Emacs. The exploration features of the ide-s were something I really missed (especially for Java development). Turned out that if you put your mind to it you can get similar results with Emacs and Vim, but it’s certainly non-trivial to get there. 🙂
I've switched to ivy and noticed all my ivy related searches start with ^. I can't seem to find the setting specifically for the initial search pattern in ivy, is something else controlling this?
actually I somehow got a search to find an article with the ^
i'm probably in an extreme minority but so far i am not liking how heavy handed the auto pair-ing functionality works in things like paredit (like I can't delete the closing paren) and smartparens, etc. Tbh, I always struggled with that in vim too. Right now i just want to go super minimal on that stuff. rainbow delimiters lets me see if i have parens balanced for now. but i know i will definitely want to have structural editing of s-expression capability, right? does emacs have built in functionality for that? if not, what is the most non invasive way to go about this? do some folks actually find they are ok without it or am i getting too minimal here and really holding myself back?
i'm not sure i follow. if you don't have balanced parens at all time how could you do structural editing?
i'm still in the learning phase so most of my programming is following along in books and tutorials and writing small functions. a lot of stuff straight in the repl. maybe i'm not grasping just how unwieldy it will eventually get?
but it will probably often do the wrong thing. "kill until this closing parens" will wipe your buffer if there is no closing parens
i can't imagine when i would ever not want a closing paren. And since everything is balanced, I can easily slurp things in, or delete entire forms at a time, etc
i see where you are going with this. in my head i was thinking you are using structural editing on an already completed function and s-expressions that you want to edit.
my main workflow is putting things in the repl so without that closing paren I can just hit enter and enter the rest of the expression like normal without it evaluating. then when i'm ready i hit Ctl-Enter and it autocompletes all the closing parens needed and evaluates. I'm suspecting this is not an idiomatic way of developing in clojure
(define-key cider-repl-mode-map (kbd "RET") #'cider-repl-newline-and-indent) (define-key cider-repl-mode-map (kbd "C-<return>") #'cider-repl-return)
@U11BV7MTK Excellent. I was just about to figure out how to do multi-line editing in the repl buffer, so thanks for sharing.
yes i have felt that pain. i think this will be much nicer for you as you learn to use structural editing
ok good. i ran into some issues ensuring there was a control-enter in terminal emacs on osx. but shouldn't be a problem for you
i use paredit. It's less "magical" and therefore predictive. I haven't ever used parinfer and i've heard some people rave about it though
i think you put it in an
:init form. I don't use use-package though so i'm not positive
can't get it to work. i'll keep trying though, i think that is basically exactly what i wanted without realizing it.
and did you put them there and then restart emacs? if you eval them manually do they work?
use package is macro-y so you probably want to put them there and then just eval-expression on those forms so they work now
got it! I just didn't have it in the right spot. sweet! thanks a bunch. I'm probably too attached to this way of working but for now it works for me and now i can slowly learn paredit without it completely overhauling my learning workflow
i'm so geeking out over emacs/lisps! i'm wondering if use-package goes against my trying to have real control over my config and learn emacs from "first principles" minimalism kind of reboot. i always loved vim-plug though cuz it just works and it is dead simple.
i think use-package gives you quite a bit of control and makes sure you do lots of things right. it makes it quite nice. if i were to start over i'd probably use it
it's also from the current maintainer of emacs so it's got some real quality behind it