4 ms·

Is there a particular tutorial or method you followed to be fluent with Paredit. I like Lisp/Scheme but have never adopted any of the tools like Paredit or Pari

by bmitc 4y ago

Is there a particular tutorial or method you followed to be fluent with Paredit. I like Lisp/Scheme but have never adopted any of the tools like Paredit or Parinfer but would be interested in doing so.

capableweb 4y ago
Seeing as you mix Lisp and Scheme together, I'm guessing you're not aiming for a specific language? If so, Calva (VS Code plugin for Clojure) has a visual guide for how to use Paredit via Calva: https://calva.io/paredit/ https://calva.io/paredit/ Even if you don't use VS Code/Clojure specifically, the "Action" names should be the same or similar with other Paredit extensions, so you can become familiar. Best advise I have for learning Paredit is doing the same as you would if you were to learn Vim: Every time you think "How can I do X faster?" look up the way to do it and write it down on a cheatsheet. After a couple of times it'll become muscle memory.
- bmitc 4y ago
  Thanks! I’ll take a look at the Calva tutorial. I’m currently not really all in on a Lisp/Scheme, as you deduced, but Racket is my usual Lisp/Scheme goto. But I’m open to using Clojure to learn.
fiddlerwoaroof 4y ago
What made a difference for me was figuring out the right keybindings. The default keybindings in emacs weren’t very ergonomic and so I came up with a more convenient set of keybindings (for evil-mode, since I prefer vim-style editing). They follow a nice pattern on the keyboard and made a huge difference. I eventually adapted them so I could have relatively consistent keybindings across vim/emacs/VSCode/IntelliJ and the results are here: https://github.com/fiddlerwoaroof/dotfiles/blob/b13240a42fa4413916ddacac62eb767f102df8c0/emacs.d/lisp/configurations/evil-conf.el#L127 https://github.com/fiddlerwoaroof/dotfiles/blob/b13240a42fa4... If you understand the elisp keybinding notation, it’s possible to use the C-, ones in VSCode.
geospeck 4y ago
When I started using Paredit I found "The Animated Guide to Paredit"[1] very helpful. It basicaly demonastrates some of the most useful commands in short videos. [1]http://danmidwood.com/content/2014/11/21/animated-paredit.html http://danmidwood.com/content/2014/11/21/animated-paredit.ht...
fm2606 4y ago
I started Emacs, Paredit and Clojure all at the same time. What helped me the most was Chapter 2 from _Clojure For The Brave and True_ (https://www.braveclojure.com/basic-emacs/ https://www.braveclojure.com/basic-emacs/). Knowing that the learning curve would be steep with emacs I cut myself a lot of slack. I've since switched from Clojure to CL but kept the elisp scripts from CFBT replacing Cider with Slime. I always thought Vim got out of my way as far as text editors go but Emacs really gets out of my way. As with most things I do I learn just enough to do what it is I want to do. I don't go searching for new things until it becomes painfully obvious that a new way needs to be found. With that said I've barely touched the surface for the power of emacs, paredit and slime.

by bmitc 4y ago

capableweb 4y ago

Seeing as you mix Lisp and Scheme together, I'm guessing you're not aiming for a specific language? If so, Calva (VS Code plugin for Clojure) has a visual guide for how to use Paredit via Calva: https://calva.io/paredit/ https://calva.io/paredit/ Even if you don't use VS Code/Clojure specifically, the "Action" names should be the same or similar with other Paredit extensions, so you can become familiar. Best advise I have for learning Paredit is doing the same as you would if you were to learn Vim: Every time you think "How can I do X faster?" look up the way to do it and write it down on a cheatsheet. After a couple of times it'll become muscle memory.

bmitc 4y ago
Thanks! I’ll take a look at the Calva tutorial. I’m currently not really all in on a Lisp/Scheme, as you deduced, but Racket is my usual Lisp/Scheme goto. But I’m open to using Clojure to learn.

fiddlerwoaroof 4y ago

What made a difference for me was figuring out the right keybindings. The default keybindings in emacs weren’t very ergonomic and so I came up with a more convenient set of keybindings (for evil-mode, since I prefer vim-style editing). They follow a nice pattern on the keyboard and made a huge difference. I eventually adapted them so I could have relatively consistent keybindings across vim/emacs/VSCode/IntelliJ and the results are here: https://github.com/fiddlerwoaroof/dotfiles/blob/b13240a42fa4413916ddacac62eb767f102df8c0/emacs.d/lisp/configurations/evil-conf.el#L127 https://github.com/fiddlerwoaroof/dotfiles/blob/b13240a42fa4... If you understand the elisp keybinding notation, it’s possible to use the C-, ones in VSCode.

geospeck 4y ago

When I started using Paredit I found "The Animated Guide to Paredit"[1] very helpful. It basicaly demonastrates some of the most useful commands in short videos. [1]http://danmidwood.com/content/2014/11/21/animated-paredit.html http://danmidwood.com/content/2014/11/21/animated-paredit.ht...

fm2606 4y ago

I started Emacs, Paredit and Clojure all at the same time. What helped me the most was Chapter 2 from _Clojure For The Brave and True_ (https://www.braveclojure.com/basic-emacs/ https://www.braveclojure.com/basic-emacs/). Knowing that the learning curve would be steep with emacs I cut myself a lot of slack. I've since switched from Clojure to CL but kept the elisp scripts from CFBT replacing Cider with Slime. I always thought Vim got out of my way as far as text editors go but Emacs really gets out of my way. As with most things I do I learn just enough to do what it is I want to do. I don't go searching for new things until it becomes painfully obvious that a new way needs to be found. With that said I've barely touched the surface for the power of emacs, paredit and slime.