GNU bug report logs - #38392
zap-up-to-char should appear in "Deletion and Killing" Emacs info section and "Command Index"

Previous Next

Full log

Message #38 received at 38392 <at> debbugs.gnu.org (full text, mbox):

From: Justin Paston-Cooper <paston.cooper <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 38392 <at> debbugs.gnu.org
Subject: Re: bug#38392: zap-up-to-char should appear in "Deletion and Killing"
 Emacs info section and "Command Index"
Date: Wed, 27 Nov 2019 20:35:03 +0100

[Message part 1 (text/plain, inline)]

Sorry for my terrible reading comprehension.

I suppose you’re saying that exactly two ‘inclusivities’ suffice: ‘up
to/until’ and 'through' in your case, which makes complete sense.

I have found that both 'up to' and 'until' are still ambiguous, for
instance when trying to agree on a date with someone. This ambiguity might
carry over to the Emacs world, where a user might not know that there is
another distinct inclusivity called 'through'. 'up to' and 'until' can mean
either 'inclusive' or 'exclusive', this seemingly depending on the phase of
the Moon. I still use the words 'inclusive' and 'exclusive' to confirm. I
hope that at least programmers don't find that silly. Of course, there is
an existing precedent of 'up to', 'until', 'through' and 'to'.

Regardless of the naming, wouldn’t an inclusivity modifier over the set of
two inclusivities be a nice thing to have?

On Wed, 27 Nov 2019 at 17:45, Drew Adams <drew.adams <at> oracle.com> wrote:

> > What about near, through and far?
>
> What about them?
>
> I've already spoken to "through".  How do you
> see "near" and "far" fitting into this?
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.