unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: 50929@debbugs.gnu.org
Subject: bug#50929: Add slurp-sexp and barf-sexp
Date: Wed, 10 Nov 2021 22:39:38 -0500	[thread overview]
Message-ID: <E1ml0w6-0004Bn-Ju@fencepost.gnu.org> (raw)
In-Reply-To: <m2lf1xnfis.fsf@me.com> (bug-gnu-emacs@gnu.org)

[[[ 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. ]]]

  > > 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-].

You can bind these keys yourself if they work ok on your terminal, but
they can't be the standard bindings.  C-< and C-> are not ASCII.
M-<left> moves by words; M-[ not possible on ttys.  C-<left> seems to be the
same as <left> on this tty.

                                                           The former two
  > > combinations are both bound to left- and right-word, and the latter two
  > > combination is unbound in emacs-lisp-mode.

  > How about us, people without the arrow keys? :) BTW, I find C-()
  > and C-{} used by Paredit fairly usable.

If `C-()' means C-( and C-), they are not in ASCII.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







      reply	other threads:[~2021-11-11  3:39 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               ` 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 [this message]

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=E1ml0w6-0004Bn-Ju@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=50929@debbugs.gnu.org \
    --cc=salutis@me.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 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).