From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#50959: [PATCH] Re: bug#50959: 28.0.50; Shorthand symbols are unknown to Emacs Date: Wed, 6 Oct 2021 21:19:17 +0100 Message-ID: References: <16338bdc2497fc51c6fb6d54ab370bfb@webmail.orcon.net.nz> <83a6jtff87.fsf@gnu.org> <5ac7a31cf2959c31c262a3377c736a5a@webmail.orcon.net.nz> <83ilygew7p.fsf@gnu.org> <83fstjdiwl.fsf@gnu.org> <837devdcz0.fsf@gnu.org> <93767e0236e7e85d27186293e38d3d25@webmail.orcon.net.nz> <8335pjd974.fsf@gnu.org> <87v92f3d15.fsf@gmail.com> <83y27bbs4d.fsf@gnu.org> <87mtnr3chk.fsf@gmail.com> <8735pj3amy.fsf@gmail.com> <83r1d3boeh.fsf@gnu.org> <874k9uwhxk.fsf_-_@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000d3cd8905cdb4dc71" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7531"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Phil Sainty , 50959@debbugs.gnu.org, Richard Stallman To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Oct 06 22:20:20 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1mYDOm-0001it-HY for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 06 Oct 2021 22:20:20 +0200 Original-Received: from localhost ([::1]:35086 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mYDOk-0000Yz-Pb for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 06 Oct 2021 16:20:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58350) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mYDOU-0000Yf-KV for bug-gnu-emacs@gnu.org; Wed, 06 Oct 2021 16:20:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34006) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mYDOU-0007cD-D3 for bug-gnu-emacs@gnu.org; Wed, 06 Oct 2021 16:20:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mYDOT-0004Wk-J9 for bug-gnu-emacs@gnu.org; Wed, 06 Oct 2021 16:20:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 06 Oct 2021 20:20:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50959 X-GNU-PR-Package: emacs Original-Received: via spool by 50959-submit@debbugs.gnu.org id=B50959.163355157417363 (code B ref 50959); Wed, 06 Oct 2021 20:20:01 +0000 Original-Received: (at 50959) by debbugs.gnu.org; 6 Oct 2021 20:19:34 +0000 Original-Received: from localhost ([127.0.0.1]:45552 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mYDO2-0004Vx-1M for submit@debbugs.gnu.org; Wed, 06 Oct 2021 16:19:34 -0400 Original-Received: from mail-pj1-f52.google.com ([209.85.216.52]:39899) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mYDO0-0004Vl-7r for 50959@debbugs.gnu.org; Wed, 06 Oct 2021 16:19:32 -0400 Original-Received: by mail-pj1-f52.google.com with SMTP id ls18-20020a17090b351200b001a00250584aso4788765pjb.4 for <50959@debbugs.gnu.org>; Wed, 06 Oct 2021 13:19:32 -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=qyfbiRqmbvj6m6W6M3RprPYCqkWqPmiWBvlanGXEOoo=; b=Lv14ERPj3QYVKkff47yLucBj+e/quCcTVknsfiDP1m9sTrC1TgN88LEyVgY90pGd9e O+uiJbLtvHTBCc4hCTMyNoQ9bOJkBg3rOZ56AVPfR+pcq/JOUQ/Q6R3xS6qMW8OyVzpu SZWtVRsWYRRH5J6nRSaPOB7jCmAxpg90Cfxez9bV9rp6iZcvuKATh3UF0nGBXOhMh8VQ LCUyILBaXAE5WR1J0CvhRUdKzxYBZcuMwGWW5V0e3i8PjWAfvPimMeid7NByOBWvWK8J lE/WBS0GTGNEL9j3yZz19uail7IyxaAsYBSJ+GJ0/FAUoH907CglG8oALxM2pEcZeSpt 6Dsw== 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=qyfbiRqmbvj6m6W6M3RprPYCqkWqPmiWBvlanGXEOoo=; b=XTZrbu4WwHhWKmLtGL+dwYCkNp5Hyu5wQYpV5DABOOPcHdUT8MFPZuHxduZBm+ZbCv rO64sAbjdtrZOqW6WiA24DLgG9qsObAD8aRgvoUcRnmeln+/RJM5zgkE8NXiXjQt5oNo kwWVT6fSzz6IIaRzGBlaU/60t6BttzAaXamu3IZEHrbJdiyQ66Fc3GfQGC0fH2Rha7/z 0TJWfDNOcJF4dHvsF+qhQD6AJkSu0jwUaNAbyMuD+npev5ORo9ZjAcKUCh+hMAavCiYf a10do+hN+PQPsJIuy6rKKQdm+8DZEzdWzrpal/Wa4T/214nxWYTiW2+pICmjYMwaQcdh aHKw== X-Gm-Message-State: AOAM5328Sms2AZZu0iVP41ADZQSg1YfmbjYaU7daSmIKNTbqpGKtiSWS TCQ2hZirchOg0iywl+57choMoCR/T60Z/SIjgeo= X-Google-Smtp-Source: ABdhPJynL5VV48ol0dSUJB9zF+eLH59QW65fgJFAyn/Sgenf3IBnQ2QLeEYDorVrHdN0PiWssUL2w4zmkHHGNXuFDvU= X-Received: by 2002:a17:90a:a60e:: with SMTP id c14mr868764pjq.70.1633551566227; Wed, 06 Oct 2021 13:19:26 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:216589 Archived-At: --000000000000d3cd8905cdb4dc71 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Oct 6, 2021 at 8:59 PM Stefan Monnier wrote: > > In this thread, we've described many ways how that can be done. > > C-x o already "pays attention" to them, from day one, but that attentio= n > > is somehow deemed insufficient. So you'll have to be clearer about > > what you're suggesting exactly, i.e., "what happens when". > > As an ELisp programmer, I'd want (and expect) that if I can successfully > use `st-bar` and `st-foo` in the current buffer, I will see them in the > possible completions at least when I complete `st-` and ideally in other > cases (e.g. it would be good for completion of `sba` to take `st-bar` > into account if `flex` completion style). > 1) If by "use in the current buffer" you mean "insert in the current buffer= " then your wish makes full sense to me and is already granted, fully, via C-M-i. 2) If you're talking about querying the single global database of symbols using M-x describe-symbols, then you must address symbols by their full name, as you have always done. It's easy to do so: 2a) by placing point under the form of interest. If it happens to be shorthand it will automatically be picked up. Shorthands are now visually highlighte= d as such. 2b) by typing the shorthands as such and typing TAB to complete them to the full symbol name. This is only if you enter the query interface from the buffer where the shorthands exist. I think this is more than sufficient. I've worked for years and years with a CL system that only does 1) and 2a). I've worked side-by-side with people using it. I even forked and maintained such a system. I've never seen requests or complaints for anything more in this regard. Sure, we are all different and some of us are more demanding, and that's a good thing, but it's a fact that the vast majority of Emacs users haven't used a namespacing system in Elisp for a long time, possibly ever. Shouldn't we give this first conservative approach a shot first? Jo=C3=A3o --000000000000d3cd8905cdb4dc71 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, Oct 6, 2021 at 8:59 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> In this thread, = we've described many ways how that can be done.
> C-x o already "pays attention" to them, from day one, but th= at attention
> is somehow deemed insufficient.=C2=A0 So you'll have to be clearer= about
> what you're suggesting exactly, i.e., "what happens when"= ;.

As an ELisp programmer, I'd want (and expect) that if I can successfull= y
use `st-bar` and `st-foo` in the current buffer, I will see them in the
possible completions at least when I complete `st-` and ideally in other cases (e.g. it would be good for completion of `sba` to take `st-bar`
into account if `flex` completion style).

1) If by "use in the current buffer" you mean "insert in = the current buffer"
then your wish makes full sense to me an= d is already granted, fully, via C-M-i.

2) If = you're talking about querying the single global database of symbols
using M-x describe-symbols, then you must address symbols by their
full name, as you have always done. It's easy to do so:
<= div>
2a) by placing point under the form of interest.=C2=A0 I= f it happens to be shorthand
it will automatically be picked up.= =C2=A0 Shorthands are now visually highlighted
as such.
=

2b) by typing the shorthands as such and typing TAB to = complete them to
the full symbol name.=C2=A0 This is only if you = enter the query interface from
the buffer where the shorthands ex= ist.

I think this is more than sufficient. I'v= e worked for years and years with
a CL system that only does 1) a= nd 2a). I've worked side-by-side with
people using it. I= even forked and maintained such a system.=C2=A0 I've never
<= div>seen requests or complaints for anything more in this regard.=C2=A0 Sur= e, we
are all different and some of us are more demanding, a= nd that's a good
thing, but it's a fact that the vast ma= jority of Emacs users haven't used
a namespacing system = in Elisp for a long time, possibly ever.=C2=A0 Shouldn't
we g= ive this first=C2=A0 conservative approach a shot first?
Jo=C3=A3o
--000000000000d3cd8905cdb4dc71--