unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Justin Paston-Cooper <paston.cooper@gmail.com>
To: Drew Adams <drew.adams@oracle.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 20:35:03 +0100	[thread overview]
Message-ID: <CAEndGgSBCo9oUFeu7OAFSrYjDdrfCyHoSnz9x0FOc96bSa6SnA@mail.gmail.com> (raw)
In-Reply-To: <22696cf2-bdb7-44d4-a586-daf1a8901250@default>

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

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@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?
>

[-- Attachment #2: Type: text/html, Size: 1799 bytes --]

  reply	other threads:[~2019-11-27 19:35 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 [this message]
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=CAEndGgSBCo9oUFeu7OAFSrYjDdrfCyHoSnz9x0FOc96bSa6SnA@mail.gmail.com \
    --to=paston.cooper@gmail.com \
    --cc=38392@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).