Paredit 25 released

Here is their release notes, this may interest most people more: https://paredit.org/cgit/paredit/plain/NEWS. For me, I have been using puni-mode as a replacement for paredit. It is more generic (using Emacs forward-sexp under the hood), therefore, more flexible. Of course there is a bit of quirks of its own. But I am fairly satisfied with it

Same here. I've started using Puni mode, replacing SmartParens, which replaced ParEdit years ago for me. I'm somewhat surprised that paredit is still around!

I was just reading about puni; it sounds great, until I got to the point about no `down-list`. Does anyone have workarounds, or other approaches?

This title is already out of date :)

Is 25 somehow no longer released?

A long time paredit user here. Turn to lispy recently, which is amazing. But paredit is still a classic piece of all time.

Did I somehow suggest that it wouldn't be?

The danger of making cheeky internet comments that require a logical leap / additional knowledge to understand is that sometimes people won't understand them.

I call this "Stallman Syndrome".

Very true. Any steps to avoid that tend to destroy any semblance of amusement, though (and on this occasion there was only a semblance to begin with at best), so I'm generally fine with the trade-off :) Although with the additional knowledge required here being a part of the linked content, I expect *most* people had observed the same thing as myself.

Work-around: use the built-in `down-list`. 🤷

🤦 There is that option! My understanding though is that won't apply to non-parentheses based modes, which isn't the end of the world but a bit inconsistent (not that my smartparens config is working well at the moment either!). I'm going to try it out anyway.

The built-in `down-list` doesn't just work with parenthesis, it works with arbitrary single-character delimiters (so braces, brackets, quotes work just fine). Does smartparens work in modes where delimiters are more than one character? Years ago when I tried smartparens for a few months the documentation *claimed* it did work with multi-character delimiters (like HTML tags or LaTeX environments) but it didn't actually work. If that's still the case, then you aren't really loosing much by using puni + down-list.

That was basically what I was referring to by "my sp config isn't working well atm"! The docs do claim that, and I *think* I remember it working, but perhaps I was using eg nxml-mode movement commands instead.

I've had paredit-mode on my eval-expression-minibuffer-setup-hook for years and it worked great, but in the last few days it prevents `<return>` from confirming the input. Is this an intended change? I can't find a place to report issues.

I contacted the author via email, and it's a known issue. A workaround is to unbind `RET` and rebind `C-j` in the `paredit-mode-map`: (define-key paredit-mode-map (kbd "RET") nil) (define-key paredit-mode-map (kbd "C-j") 'paredit-newline)