From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Justin Paston-Cooper Newsgroups: gmane.emacs.bugs 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 Message-ID: References: <83wobmqv4p.fsf@gnu.org> <83v9r6qu8c.fsf@gnu.org> <4eba4e99-0aa0-4194-a5d1-842b039e377d@default> <22696cf2-bdb7-44d4-a586-daf1a8901250@default> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000008c6a39059859187c" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="170147"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 38392@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Nov 27 20:39:27 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ia39o-000i3f-U8 for geb-bug-gnu-emacs@m.gmane.org; Wed, 27 Nov 2019 20:39:25 +0100 Original-Received: from localhost ([::1]:42428 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ia39m-0008R9-UE for geb-bug-gnu-emacs@m.gmane.org; Wed, 27 Nov 2019 14:39:22 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44058) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ia36Z-0004p7-T3 for bug-gnu-emacs@gnu.org; Wed, 27 Nov 2019 14:36:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ia36Y-0002IN-R6 for bug-gnu-emacs@gnu.org; Wed, 27 Nov 2019 14:36:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50261) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ia36Y-0002I2-NP for bug-gnu-emacs@gnu.org; Wed, 27 Nov 2019 14:36:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ia36Y-0004XH-IR for bug-gnu-emacs@gnu.org; Wed, 27 Nov 2019 14:36:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Justin Paston-Cooper Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 27 Nov 2019 19:36:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38392 X-GNU-PR-Package: emacs Original-Received: via spool by 38392-submit@debbugs.gnu.org id=B38392.157488332317384 (code B ref 38392); Wed, 27 Nov 2019 19:36:02 +0000 Original-Received: (at 38392) by debbugs.gnu.org; 27 Nov 2019 19:35:23 +0000 Original-Received: from localhost ([127.0.0.1]:56234 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ia35u-0004WK-PT for submit@debbugs.gnu.org; Wed, 27 Nov 2019 14:35:23 -0500 Original-Received: from mail-io1-f53.google.com ([209.85.166.53]:47052) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ia35s-0004Vz-S2 for 38392@debbugs.gnu.org; Wed, 27 Nov 2019 14:35:21 -0500 Original-Received: by mail-io1-f53.google.com with SMTP id i11so26124569iol.13 for <38392@debbugs.gnu.org>; Wed, 27 Nov 2019 11:35:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ha23Fk1GOB2gpdKsEs/zWDa7wInuM+i7YamauDgoJZ0=; b=MySUewPKzxGtNaPTbRn7pmJAcNeYFvx+Ycqnc9SQosEgN3l9FjQrEuuRoYEJ8igzPr +F1ythF8c6Zgd5AvWtdvyl+gHiffAT54lqiUvWI+p2RgB3LpEOhKweJhcQ+k9OCv67gL TGuyJ2mvBN6nj9noUxtQU7budlYkLIwZTAPE54msUZgvdOI8tE2ml70FoL9zm1WRZQ5T i0ju7tY/nEcXtbn1ZxRh5u6I5BYqU4C5VNaPlLHyv3pMjKkfDI9BurmTrz2XqSZK0YqX L75XvmDgRh2zmCsHGYz1/j2p0rkdKwlpe34oLHcamYBJ814jmqwPocuMaa574Q/JwQyL xWig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ha23Fk1GOB2gpdKsEs/zWDa7wInuM+i7YamauDgoJZ0=; b=l2xDo7RBRS64xuYqO2Fs6cK/Bf1ckYmqZP2QOvZrW+iNJRtK7RZhKHYga5Iom6cq4r bqWWwWM+KIpK8czS+yXpyGY9ESrlhsNqxFllntjlxEv/D8uYqgVuDEpDyJP+vt3WbGLL mryy1sZHVqDXlkXhhd4nOI6kWqKuIB0QSP6FqeP1Zd5bEd1b1Nqbec1CYNPCv60AiNWX sTm/0ecEQlgypig0uM+82Ivm1GmROme7Ukerqd8tp/cfhIEZOanEAOJ0V43zgHJZg8zB r4jz4aXsBd8eLPCQ/gkTBH6/89pYFkYDk3xlPvKZm+rGNAA5IFbWG/EdfvIJb9bZ4AuA 0F1w== X-Gm-Message-State: APjAAAVtBaaKSJt4JK1VU4C7axzTUVSpU6UBjcrLQ9lC8fyX8Fa4IpxI tV+Os9NVTBJMZHhGON/6WDhnqiwNH0m7+NNVvMM= X-Google-Smtp-Source: APXvYqw5ZSRbwjG5eRAAvrWcV2LT/+4vZ4FpdgHVEot02iSpq+3zv24us3o4eEbpoWP4ZgnDmg9roc1IfzkobnBhPjU= X-Received: by 2002:a02:cb4d:: with SMTP id k13mr1620437jap.89.1574883314917; Wed, 27 Nov 2019 11:35:14 -0800 (PST) In-Reply-To: <22696cf2-bdb7-44d4-a586-daf1a8901250@default> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:172553 Archived-At: --0000000000008c6a39059859187c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry for my terrible reading comprehension. I suppose you=E2=80=99re saying that exactly two =E2=80=98inclusivities=E2= =80=99 suffice: =E2=80=98up to/until=E2=80=99 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=E2=80=99t 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 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? > --0000000000008c6a39059859187c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry for my terrible reading = comprehension.

I suppose you=E2=80=99re saying that exactly two =E2=80=98inclusivities= =E2=80=99 suffice: =E2=80=98up to/until=E2=80=99 and 'through' in y= our case, which makes complete sense.

I have found that both 'up to' and 'until' ar= e 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 no= t 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, the= re is an existing precedent of 'up to', 'until', 'throu= gh' and 'to'.

Regardless of the naming, wouldn=E2=80=99t an inclusivity modifier ov= er 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, throug= h and far?

What about them?

I've already spoken to "through".=C2=A0 How do you
see "near" and "far" fitting into this?
--0000000000008c6a39059859187c--