unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Justin Paston-Cooper <paston.cooper@gmail.com>, 38392@debbugs.gnu.org
Subject: bug#38392: zap-up-to-char should appear in "Deletion and Killing" Emacs info section and "Command Index"
Date: Thu, 28 Nov 2019 08:42:32 -0800 (PST)	[thread overview]
Message-ID: <90186505-3129-402f-8bc2-babe7fed6991@default> (raw)
In-Reply-To: <87mucgjr1e.fsf@marxist.se>

> > 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").
> 
> FWIW, I think `zap-until-char' and `zap-through-char' would be less
> clear than the current names.
> 
> I agree with the point about consistency.  It would be better then to
> rename `isearch-yank-until-char' to `isearch-yank-up-to-char' instead
> of renaming the old commands, I think.

No objection from me.

Consistency can help in general, but it's not an
imperative.  More important than global consistency
is local consistency (e.g. within Isearch, don't use
more than one way to name the same thing).

It's probably too late to change `zap-to-char', but
I think that `through' is clearer than `to', when
the char is included.  `zap-through-char' would be
clearer, and it's confusing to have both `-to-' and
`-up-to-'.

(There currently is no Isearch yank command that has
"through" semantics, but I added a couple in my code
and in the patch I submitted for bug #37417.)





  reply	other threads:[~2019-11-28 16:42 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
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 [this message]
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=90186505-3129-402f-8bc2-babe7fed6991@default \
    --to=drew.adams@oracle.com \
    --cc=38392@debbugs.gnu.org \
    --cc=paston.cooper@gmail.com \
    --cc=stefan@marxist.se \
    /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).