From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: Do shorthands break basic tooling (tags, grep, etc)? (was Re: Shorthands have landed on master) Date: Tue, 5 Oct 2021 23:07:02 +0100 Message-ID: References: <16338bdc2497fc51c6fb6d54ab370bfb@webmail.orcon.net.nz> <831r59kyhf.fsf@gnu.org> <834ka4k15m.fsf@gnu.org> <83y27gijmz.fsf@gnu.org> <8335pmgnjy.fsf@gnu.org> <604da2cb10ac61f2b8b89a02c89056be@webmail.orcon.net.nz> <83a6jtff87.fsf@gnu.org> <5ac7a31cf2959c31c262a3377c736a5a@webmail.orcon.net.nz> <83ilygew7p.fsf@gnu.org> <83fstjdiwl.fsf@gnu.org> <871r534s2o.fsf@gmail.com> <87sfxgx09x.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000095b89905cda24070" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30241"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Phil Sainty , Alan Mackenzie , Eli Zaretskii , emacs-devel To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 06 00:09:26 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mXsco-0007fm-0A for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Oct 2021 00:09:26 +0200 Original-Received: from localhost ([::1]:53596 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mXscm-0004u2-Gg for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Oct 2021 18:09:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49064) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mXsam-0003Yq-M3 for emacs-devel@gnu.org; Tue, 05 Oct 2021 18:07:20 -0400 Original-Received: from mail-pg1-x535.google.com ([2607:f8b0:4864:20::535]:35682) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mXsak-0000mA-9h; Tue, 05 Oct 2021 18:07:19 -0400 Original-Received: by mail-pg1-x535.google.com with SMTP id e7so652954pgk.2; Tue, 05 Oct 2021 15:07:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mME7RCmOsJLpxWEdjATt6ZhBVFTTYpZJvhQUn8GlyEg=; b=XI5WuNe/b3WSSpZTSCaY6Ij7kElALDniQHgSE3ZfibwMsdcDgh/S7Yp6TJzvISrh3M di4NxMyB5FYIPLanLn1EWlu3+QkSWjuhAPVvF6hT0Rtv3hT+wWP9GH+UlNKtc20Uo+tY FdGU7BMiBf2ch/aVhqrRjwZRgmUDs+ezUFHV1Nhg8SgAPG8yqeyxD4N5FYiDmwplzzED I6krotBmgF510hM2EVV0JZzZ4zcxUt7/9kJwBgC/tIy7fikXGYVXgR5VnDFx4VGshAIX h3RU0Shf+sEMgilM7E4EMpMZ1w1nkxpCebERBRuf0UHGssU0FGVjlXKZbCCZwaZAMDh0 lVCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mME7RCmOsJLpxWEdjATt6ZhBVFTTYpZJvhQUn8GlyEg=; b=f+SGfPO5m/XzwBEyUJdTEKYEWXht/44Sr8ddesiPSJvsKuBrQrnzAgZ1vnX/YR/qp6 3qI0xY0C+c4gFuoFqcIzAWZ+iNkhNbq6hYxajDnuKmjRvpC2XmPmLHb/Ihb8GISVdMKK jedoBeniyyUjK6d+FYlU2R1Be0s5W6CD1QsjmC3sZbBcTubGSb4AhfoIcq1pA7nC6Ijt Nht4GkwbH3mD54rlBVvPlAAclPJtmrHFtkVoSkyzLPwT56+9lLd92oGUoErz/KQKkG0g mw8E/FIWn/3XDQg0NslVcfyRsfO07ZVh7pdR6HPIBS2bc76HF0Ymi4IzMKigpY4QEsyA zbDw== X-Gm-Message-State: AOAM531ihNvdLK0/XSaCe2bYviwF+F/QPF5h+PK4+dOmEQld9dwIhqXX 4Em/sXHQIFxKFP82dfnW9KjuU3fMcMiGc2rhZ1t2wtD9 X-Google-Smtp-Source: ABdhPJz9vSB7fBK1GyZ94+vJaxTNfZsW5o410XLG7bo6AbYZMF8axnHcBXaJGIlPWr5imBs5wjc2BWy5yTfc1QqRJvk= X-Received: by 2002:a05:6a00:24d0:b0:448:29d1:518f with SMTP id d16-20020a056a0024d000b0044829d1518fmr34068916pfv.72.1633471635502; Tue, 05 Oct 2021 15:07:15 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=2607:f8b0:4864:20::535; envelope-from=joaotavora@gmail.com; helo=mail-pg1-x535.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:276395 Archived-At: --00000000000095b89905cda24070 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Oct 5, 2021, 22:20 Richard Stallman wrote: > That would be a non-trivial effort and would bring grave confusion. > > I don't see that it would cause grave confusion. > It would for me. I'd have to keep in mind exactly where I'm invoking help commands from. I've never done that. > > > That's because, as you have well written elsewhere, the Lisp reader > > follows 's-foo' to 'string-library-foo' on this buffer but may foll= ow > > it to 'system-library-foo' in another buffer. > > That is true. > > If the extension I proposed for C-h o is made, then C-h o s-foo RET > would present info on 'string-library-foo' in one buffer, and about > 'system-library-foo' in another buffer. But if the help buffer > explains this clearly, it will make sense to the user, and it will be > useful. > Yes, you're right. If we're clear about what we're sitting the user, it's not so bad. That option is on the table. Another simpler, less "revolutionary" option (can't find the right word) is to do what Eli suggested, having 'C-h f s-foo TAB' expand to the actual symbol name, according to the buffer, using the normal completion mechanisms of Emacs. Then the usual invariant of 'C-h f' showing global symbols would be kept. We can upgrade from Eli's suggestion (which would seem simpler to implement), to your suggestion later. Jo=C3=A3o > --00000000000095b89905cda24070 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Oct 5, 2021, 22:20 Richard Stallman <rms@gnu.org> wrote:

=C2=A0 >=C2=A0 =C2=A0That would be a non-trivial effort and would bring = grave confusion.

I don't see that it would cause grave confusion.
=

It would for me. I'= d have to keep in mind exactly where I'm invoking help commands from. I= 've never done that.
=

=C2=A0 >=C2=A0 =C2=A0That's because, as you have well written elsewh= ere, the Lisp reader
=C2=A0 >=C2=A0 =C2=A0follows 's-foo' to 'string-library-foo&= #39; on this buffer but may follow
=C2=A0 >=C2=A0 =C2=A0it to 'system-library-foo' in another buffe= r.

That is true.

If the extension I proposed for C-h o is made, then C-h o s-foo RET
would present info on 'string-library-foo' in one buffer, and about=
'system-library-foo' in another buffer.=C2=A0 But if the help buffe= r
explains this clearly, it will make sense to the user, and it will be
useful.

Yes, you're right. If we're clear about what we're sitti= ng the user, it's not so bad. That option is on the table.

Another simpler, less "revoluti= onary" option (can't find the right word) is to do what Eli sugges= ted, having 'C-h f s-foo TAB' expand to the actual symbol name, acc= ording to the buffer, using the normal completion mechanisms of Emacs. Then= the usual invariant of 'C-h f' showing global symbols would be kep= t.

We can upgrade from E= li's suggestion (which would seem simpler to implement), to your sugges= tion later.=C2=A0

Jo=C3= =A3o
--00000000000095b89905cda24070--