https://www.emacswiki.org/emacs/ParEdit
edit: paredit demos:
Productive Emacs: Paredit https://www.youtube.com/watch?v=T1WBsI3gdDE
Emacs Rocks! Episode 14: Paredit: https://www.youtube.com/watch?v=D6h5dFyyUX0
https://www.emacswiki.org/emacs/ParEdit
edit: paredit demos:
Productive Emacs: Paredit https://www.youtube.com/watch?v=T1WBsI3gdDE
Emacs Rocks! Episode 14: Paredit: https://www.youtube.com/watch?v=D6h5dFyyUX0
By comparison, the Emacs Wiki article is a poor introduction, because introduction is not its purpose; it's there to collect resources for people who already use paredit, and a good introduction answers the question of why someonr would want to start.
That said, thanks so much for posting about it here! I'm really looking forward to learning it today.
I pretty much just use indented text trees for all but the most complex parts of software design and I find it works very well.
You mean points and sub-points?
>all but the most complex parts
And what do you use for those?
I've never used it and I'm genuinely curious.
If I was working on lisp-like languages, I would definitely use it. But ParEdit didn't stick to me, even after a few attempts. I didn't like the key bindings, and I think that the interface is too complex for me.
Also, there are alternatives. What do you think about them?
Not sure what it is like for other tree structures.