home.social

#paredit — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #paredit, aggregated by home.social.

  1. Just like humans, AI agents really struggle to get the parentheses in #Clojure properly balanced. Only #Paredit is always right in this regard.

  2. Also from a "designer"-perspective, due to its simple tree structure editing #SXML with #paredit or #parinfer or #lispy or #treesitter any whatever structural editor you use is like playing with #legos

  3. i've only ever seen proper structural editing with lisps. in emacs you have things like paredit. and i get it, parsing lisp is trivial, text wrapped in pairs of parantheses are your parse nodes. but we have treesitter. we can do so much more.

    i could just write code and not care about syntax at all. i shouldn't ever have to fight it. and my editor should be a parse tree editor, not a text editor. text just isn't my interface most of the time. if i'm writing prose, maybe. but usually, i'm not.

    when i hit w in vim style binds often mean to go to the next sibling node. but i'm having to spam that and some amount of h or l to get to where i want to go. when writing code i don't think in words or characters. when i hit j i often mean to go to the next statement or expression.

    #lisp #paredit #emacs #vim #treesitter

  4. thoughts on #paredit upon first look: Nice. i especially like the bindings of C-M-p and C-M-n. don't like how it rebinds C-left and C-right because i actually use those sometimes to move around, but the new functionality they have is useful and i can just rebind that to M-left and M-right. might actually add this to my #emacs config. for now i will go to bed

  5. Hey people, what binding do you use for the paredit-backward-* commands since `C-M-<left>` and `C-M-<right>` are used by Gnome to switch workspaces?

  6. If manipulating syntax trees counts as a form of structural editing then all editors that support lisp are technically structural editors.

    /hj

    With paredit (or smartparens, etc) this becomes less of a half-joke -- the "tree" always remains valid!

    #lisp #paredit #structureeditor

  7. For a while now my `eval-expression` in Emacs was broken and I never bothered to investigate.. Hitting RET in the minibuffer didn't evaluate the expression and instead inserted a newline.

    Turns out paredit binds RET in it's keymap to `paredit-RET`.

    This fix worked for me:
    ```
    (define-key paredit-mode-map (kbd "RET") nil)
    ```

    Source: old.reddit.com/r/emacs/comment

    #emacs #paredit

  8. What other reason do you need to use #emacs ?

    #paredit could be the just enough reason. It is too powerful.

    Don't edit text, that is too 21 century. Edit Abstract Syntax Trees 😘

    youtube.com/watch?v=D6h5dFyyUX

  9. How do you make paredit work when editing elisp in Org mode's code blocks?

    It's like I don't have paredit at all in code blocks. Structural editing doesn't work at all. I'm back to editing characters 🙁

    #emacs #orgmode #paredit #scheme #elisp #lisp

  10. Spending a lot of time in Scheme. I think I'm finally at the point where retraining my fingers to use paredit makes sense. My first attempts spiraled into swearing sessions since it doesn't let you unbalance parens. I get why it does this but it was a bit much while trying to get used to sexps.

    #programming #emacs #lisp #scheme #guile #paredit

  11. Replaced #paredit with #puni plus built-in electric-pair mode in my #emacs configuration.

    Much simpler, same features (at least the one that I use) and less "exceptions" for paredit.

    github.com/AmaiKinono/puni

  12. @bjc yeah, I disabled #paredit and the problem's gone. Thanks again for the hint 🙂

    I see that there have been recent updates to paredit upstream. They even have a new website: paredit.org/

    And there's a version 27 beta. I think I'll check if I can reproduce the problem in that version when I get some time.