From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Simplification of `affixation-function` Date: Wed, 28 Apr 2021 22:59:51 +0300 Organization: LINKOV.NET Message-ID: <87y2d2sp18.fsf@mail.linkov.net> References: <87y2d777r2.fsf@mail.linkov.net> <35e2e508-cd0a-b921-af96-9c12da92faf3@yandex.ru> <126afe1f-8ac5-69fc-f6af-a586bc354d03@daniel-mendler.de> <1e9bb418-9f1a-68ee-14de-e68f30f88b0a@daniel-mendler.de> <50cfaa6f-67c0-117f-41b5-10fefabee0d2@yandex.ru> <8735vbr7w3.fsf@mail.linkov.net> <35eddaa5-30fa-80db-7a29-3d171b5c09d6@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26850"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: Daniel Mendler , Stefan Monnier , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 28 22:03:30 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 1lbqPC-0006tX-TV for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Apr 2021 22:03:30 +0200 Original-Received: from localhost ([::1]:34930 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lbqPB-000246-Vo for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Apr 2021 16:03:30 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33766) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lbqMk-0008N5-7n for emacs-devel@gnu.org; Wed, 28 Apr 2021 16:00:58 -0400 Original-Received: from relay2-d.mail.gandi.net ([217.70.183.194]:49859) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lbqMa-0001oi-JK for emacs-devel@gnu.org; Wed, 28 Apr 2021 16:00:57 -0400 X-Originating-IP: 91.129.102.166 Original-Received: from mail.gandi.net (m91-129-102-166.cust.tele2.ee [91.129.102.166]) (Authenticated sender: juri@linkov.net) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 4FDE040007; Wed, 28 Apr 2021 20:00:41 +0000 (UTC) In-Reply-To: <35eddaa5-30fa-80db-7a29-3d171b5c09d6@yandex.ru> (Dmitry Gutov's message of "Wed, 28 Apr 2021 03:20:31 +0300") Received-SPF: pass client-ip=217.70.183.194; envelope-from=juri@linkov.net; helo=relay2-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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:268587 Archived-At: >> Then the caller e.g. help--symbol-completion-table could define whether >> to append "u", "a" and "c" in parens by using on a candidate something like >> (format "%s (%s)" cand (cond ((fboundp (intern cand)) "f")) ...), >> or prepend a dimmed letter as a prefix, or to use an icon. > > Do you use Company? Take a look at what elisp--company-kind does. > > The fact that the space of allowed values is constrained makes the returned > information really more useful. > > And here since you do not document which values (strings, characters, etc) > the prefix returned by affixation-function can take, their usefulness is > limited. The user can't be sure what "c" means: it's "command" here, but > could be meant as "constant" by another affixation function. Is "m" > a "macro" or "method"? "f" stands for "function" or "field"? > > And also because of that no completing-read UI can replace these characters > with any alternative (e.g. graphical) representation. I took a look at elisp--company-kind and see such code: :annotation-function (lambda (str) (if (fboundp (intern-soft str)) " ")) :company-kind #'elisp--company-kind There are still hard-coded letters where "f" stands for "function".