From: Drew Adams <drew.adams@oracle.com>
To: Justin Paston-Cooper <paston.cooper@gmail.com>
Cc: 38392@debbugs.gnu.org
Subject: bug#38392: zap-up-to-char should appear in "Deletion and Killing" Emacs info section and "Command Index"
Date: Wed, 27 Nov 2019 08:04:06 -0800 (PST) [thread overview]
Message-ID: <eeacfde0-b61f-49d3-b594-e0c2307200cf@default> (raw)
In-Reply-To: <CAEndGgRgre5q5NHhdGydsLtyonkoPBZYo3u=EqV3+tOCwjE=pA@mail.gmail.com>
> What about having a class of inclusivity modifiers of the form `C-I
> element` (I is isomorphic to set of inclusivities {before, through,
^^^^^^
> after}),
^^^^^
> element is either RET for defining inclusivity alone, or a
> `regexp RET` for including a certain pattern, similar to C-u, which
> would pass an argument to things like C-f, C-b, C-s and do the
> appropriate?
Just a comment about "before" and "after":
Those terms should be used only if the functionality
really does proceed in a particular buffer direction.
For example, the proposed Isearch commands I
mentioned, which have names with "through", can
work in either forward or backward direction, so
in their case "after" or "before" would be wrong,
for the command name.
next prev parent reply other threads:[~2019-11-27 16:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 18:34 bug#38392: zap-up-to-char should appear in "Deletion and Killing" Emacs info section and "Command Index" Justin Paston-Cooper
2019-11-26 19:45 ` Eli Zaretskii
2019-11-26 19:47 ` Justin Paston-Cooper
2019-11-26 20:05 ` Eli Zaretskii
2019-11-27 10:11 ` Justin Paston-Cooper
2019-11-27 15:40 ` Drew Adams
2019-11-27 15:57 ` Justin Paston-Cooper
2019-11-27 16:04 ` Drew Adams [this message]
2019-11-27 16:05 ` Justin Paston-Cooper
2019-11-27 16:44 ` Drew Adams
2019-11-27 19:35 ` Justin Paston-Cooper
2019-11-27 21:46 ` Drew Adams
2019-11-27 22:10 ` Justin Paston-Cooper
2019-11-28 0:45 ` Phil Sainty
2019-11-28 12:48 ` Lars Ingebrigtsen
2019-11-29 12:15 ` Stefan Kangas
2019-12-05 9:56 ` Lars Ingebrigtsen
2019-11-29 10:19 ` Eli Zaretskii
2019-11-28 9:20 ` Stefan Kangas
2019-11-28 16:42 ` Drew Adams
2019-11-27 15:54 ` Eli Zaretskii
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=eeacfde0-b61f-49d3-b594-e0c2307200cf@default \
--to=drew.adams@oracle.com \
--cc=38392@debbugs.gnu.org \
--cc=paston.cooper@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 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).