From: Lars Ingebrigtsen <larsi@gnus.org>
To: Liang-Jie Lee <s930054123yaoyao@gmail.com>
Cc: 49598@debbugs.gnu.org
Subject: bug#49598: 28.0.50; [Feature Request] Support slurping and barfing operations in lisp-mode
Date: Sat, 17 Jul 2021 16:21:05 +0200 [thread overview]
Message-ID: <87zgul3tta.fsf@gnus.org> (raw)
In-Reply-To: <871r7yqm7c.fsf@gmail.com> (Liang-Jie Lee's message of "Sat, 17 Jul 2021 00:04:39 +0800")
Liang-Jie Lee <s930054123yaoyao@gmail.com> writes:
> Slurping is the operation to expand current S-expression by pulling in
> the next outer S-expression, for example (| is cursor):
>
> (foo (bar |baz) abc efg) -> (foo (bar |baz abc) efg)
>
> Barfing is the opposite, contracting the S-expression by pushing out
> it's last-most form, for example:
>
> (foo (bar |baz abc) efg) -> (foo (bar |baz) abc efg)
I'm not quite sure what the request is here -- to add key bindings for
`paredit-forward-slurp-sexp' and `paredit-forward-barf-sexp' to
`emacs-lisp-mode? (Or `lisp-mode-shared-map', I guess...)
I'm not sure these are commands that are generally used that much to
warrant doing that, and I think people that are really into these things
just enable paredit mode (or something similar).
But I may be wrong in that -- if there's a clamouring for these commands
having a key binding in Lispish modes, I wouldn't be against adding
them. What do the rest of you people think?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-17 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 16:04 bug#49598: 28.0.50; [Feature Request] Support slurping and barfing operations in lisp-mode Liang-Jie Lee
2021-07-16 20:25 ` Eduardo Ochs
2021-07-19 0:06 ` Richard Stallman
2021-07-17 14:21 ` Lars Ingebrigtsen [this message]
2021-08-16 12:14 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgul3tta.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=49598@debbugs.gnu.org \
--cc=s930054123yaoyao@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.