From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#38392: zap-up-to-char should appear in "Deletion and Killing" Emacs info section and "Command Index" Date: Thu, 28 Nov 2019 10:20:29 +0100 Message-ID: <87mucgjr1e.fsf@marxist.se> References: <83wobmqv4p.fsf@gnu.org> <83v9r6qu8c.fsf@gnu.org> <4eba4e99-0aa0-4194-a5d1-842b039e377d@default> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="65679"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Justin Paston-Cooper , 38392@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Nov 28 10:25:52 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 1iaG3b-000GvG-GM for geb-bug-gnu-emacs@m.gmane.org; Thu, 28 Nov 2019 10:25:51 +0100 Original-Received: from localhost ([::1]:46888 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iaG3Z-0003Ux-S3 for geb-bug-gnu-emacs@m.gmane.org; Thu, 28 Nov 2019 04:25:49 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34126) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iaFz0-00025V-Qf for bug-gnu-emacs@gnu.org; Thu, 28 Nov 2019 04:21:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iaFyy-0001SZ-MZ for bug-gnu-emacs@gnu.org; Thu, 28 Nov 2019 04:21:05 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50649) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iaFyy-0001QM-9k for bug-gnu-emacs@gnu.org; Thu, 28 Nov 2019 04:21:04 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iaFyw-0003w1-S9 for bug-gnu-emacs@gnu.org; Thu, 28 Nov 2019 04:21:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 28 Nov 2019 09:21: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.157493284315071 (code B ref 38392); Thu, 28 Nov 2019 09:21:02 +0000 Original-Received: (at 38392) by debbugs.gnu.org; 28 Nov 2019 09:20:43 +0000 Original-Received: from localhost ([127.0.0.1]:56618 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iaFyd-0003v0-33 for submit@debbugs.gnu.org; Thu, 28 Nov 2019 04:20:43 -0500 Original-Received: from ted.gofardesign.uk ([67.225.143.91]:47814) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iaFya-0003ui-Ic for 38392@debbugs.gnu.org; Thu, 28 Nov 2019 04:20:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=marxist.se; s=default; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=AS013ikRSdC7j22GX3Cqp7xqjYDRe2KzLtW41m0lhsU=; b=odyw6nAOYCZ9gwNZoF5+wwPMDO h6muqtqZu0mAECux98npD/j0eH9xfB+xvDPG2OyMe6p5SBN1oBxYEiR+DuWckv0ZBYTDVxtopYJmD SlKrTJ09G848r8G/w5CKFkZHtMW2Y7D+YKDopsAdB37vuHa9RpUUEPSSZikFaW9b40jYAqL8i9oM2 1Qyu9mWlMyd892cDjpfFH7yaamEYgzRcNWMsatzry/E8nrRB/3egRxCyPqh6lEwu6h0cvJ4M5my7a CltabASH8EIG1hO2omMliSTQqXq7j/izQ0m7AFs3RKedOH024kpfwFbwhHmg2ZYod/0+uBvoW4+0p haOsW/NQ==; Original-Received: from h-70-69.a785.priv.bahnhof.se ([155.4.70.69]:41848 helo=localhost) by ted.gofardesign.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1iaFyR-000jZf-U1; Thu, 28 Nov 2019 04:20:32 -0500 In-Reply-To: <4eba4e99-0aa0-4194-a5d1-842b039e377d@default> (Drew Adams's message of "Wed, 27 Nov 2019 07:40:25 -0800 (PST)") X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ted.gofardesign.uk X-AntiAbuse: Original Domain - debbugs.gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - marxist.se X-Get-Message-Sender-Via: ted.gofardesign.uk: authenticated_id: stefan@marxist.se X-Authenticated-Sender: ted.gofardesign.uk: stefan@marxist.se 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:172588 Archived-At: Drew Adams writes: > 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. Best regards, Stefan Kangas