From: Drew Adams <drew.adams@oracle.com>
To: Justin Paston-Cooper <paston.cooper@gmail.com>,
Eli Zaretskii <eliz@gnu.org>
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 07:40:25 -0800 (PST) [thread overview]
Message-ID: <4eba4e99-0aa0-4194-a5d1-842b039e377d@default> (raw)
In-Reply-To: <CAEndGgTwM0pXqGtLKweZYK68EAV0yPBj-kYfZeTWoWtTTpLcFg@mail.gmail.com>
> not zap-***up***-to-char.
In Isearch we now have `isearch-yank-until-char'.
So we now have two different ways to name something
that deals with text from point forward to, but not
including, the position of some char: "up to" vs
"until".
It would be better to have a single way to name this.
---
Considering that the names `zap-to-char' and
`zap-up-to-char' are so close, and they can be
confused (witness Eli's missing the difference
here, at first), "until" seems a bit better.
On the other hand, "until" has a strong connotation
of time, and a weak one of space/distance. And "up
to" is pretty clear, if taken apart from "to".
Really, `zap-to-char' should probably be called
`zap-through-char'. I'd suggest using the terms
"until" (for "up to") and "through" (for zap "to").
In the improvements I suggested for Isearch (bug
#37417, emacs-devel thread "PATCH:
isearch-yank-until-match" and part of thread
"PATCH: isearch-yank-until-char"), I used
"through" for commands that act from point through
some position: `isearch-yank-through-new-match',
`isearch-yank-through-key-move', and
`isearch-yank-through-rec-edit-move'.
next prev parent reply other threads:[~2019-11-27 15:40 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 [this message]
2019-11-27 15:57 ` Justin Paston-Cooper
2019-11-27 16:04 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4eba4e99-0aa0-4194-a5d1-842b039e377d@default \
--to=drew.adams@oracle.com \
--cc=38392@debbugs.gnu.org \
--cc=eliz@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 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.