From: Philip Kaludercic <philipk@posteo.net>
To: Richard Stallman <rms@gnu.org>
Cc: larsi@gnus.org, 50929@debbugs.gnu.org
Subject: bug#50929: Add slurp-sexp and barf-sexp
Date: Tue, 09 Nov 2021 12:13:29 +0000 [thread overview]
Message-ID: <87wnlhy1au.fsf@posteo.net> (raw)
In-Reply-To: <E1mkPSf-00051j-B4@fencepost.gnu.org> (Richard Stallman's message of "Tue, 09 Nov 2021 06:38:45 -0500")
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> Thanks for explaining. I think these commands will be useful if they
> have short enough key sequences -- can we find short enough ones to
> give them?
I use C-<left> and C-<right>, but alternatives I can think of are
M-<left> and M-<right>, C-< and C-> or M-[ and M-]. The former two
combinations are both bound to left- and right-word, and the latter two
combination is unbound in emacs-lisp-mode.
> I think `swallow-sexp' and `disgorge-sexp' are better names.
I like these too.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-11-09 12:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 7:43 bug#50929: Add slurp-sexp and barf-sexp Philip Kaludercic
2021-10-01 8:12 ` Lars Ingebrigtsen
2021-10-01 8:31 ` Philip Kaludercic
2021-11-05 3:04 ` Lars Ingebrigtsen
2021-11-06 18:53 ` Juri Linkov
2021-11-08 3:08 ` Richard Stallman
2021-11-08 15:23 ` Philip Kaludercic
2021-11-09 11:38 ` Richard Stallman
2021-11-09 12:13 ` Philip Kaludercic [this message]
2021-11-09 16:26 ` bug#50929: [External] : " Drew Adams
2021-11-09 18:44 ` Philip Kaludercic
2021-11-09 19:15 ` Drew Adams
2021-11-09 22:17 ` Drew Adams
2021-11-11 3:39 ` Richard Stallman
2021-11-14 0:05 ` Philip Kaludercic
2021-11-14 17:32 ` Drew Adams
2021-11-09 22:14 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-11 3:39 ` Richard Stallman
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=87wnlhy1au.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=50929@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
/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.