From: Drew Adams <drew.adams@oracle.com>
To: Philip Kaludercic <philipk@posteo.net>, Richard Stallman <rms@gnu.org>
Cc: "larsi@gnus.org" <larsi@gnus.org>,
"50929@debbugs.gnu.org" <50929@debbugs.gnu.org>
Subject: bug#50929: [External] : bug#50929: Add slurp-sexp and barf-sexp
Date: Tue, 9 Nov 2021 16:26:36 +0000 [thread overview]
Message-ID: <SJ0PR10MB548810A2CF0A54B0E6D2299BF3929@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87wnlhy1au.fsf@posteo.net>
> 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.
FWIW -
I'd prefer that no default key bindings be sacrificed
for this. This kind of editing is mostly appropriate
for use with "structured editing" modes that
automatically and always pair delimiters. I think it
makes most sense for only such modes to bind keys for
such commands.
next prev parent reply other threads:[~2021-11-09 16:26 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
2021-11-09 16:26 ` Drew Adams [this message]
2021-11-09 18:44 ` bug#50929: [External] : " 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB548810A2CF0A54B0E6D2299BF3929@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=50929@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=philipk@posteo.net \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).