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: [PATCH] (icomplete-vertical-mode): Add support for affixations and, annotations Date: Tue, 25 May 2021 19:59:25 +0300 Organization: LINKOV.NET Message-ID: <87tumq92pe.fsf@mail.linkov.net> References: <87zgwlb4xc.fsf@gmail.com> <617d06ca-27bf-2ae8-26eb-1042123499d3@daniel-mendler.de> <87pmxhb1rs.fsf@gmail.com> <23510125-37b9-e87e-3590-5322f44772ce@daniel-mendler.de> <87y2c5nhsr.fsf@mail.linkov.net> <87h7irss50.fsf@mail.linkov.net> <43d1599e-2ba9-2efb-45c3-76c67d29a69d@daniel-mendler.de> <87tumrgqrb.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17330"; 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 , Dmitry Gutov , monnier@iro.umontreal.ca, "emacs-devel@gnu.org" To: =?iso-8859-1?Q?Jo=E3o_T=E1vora?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 25 19:25:56 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 1llaoW-0004Nx-5T for ged-emacs-devel@m.gmane-mx.org; Tue, 25 May 2021 19:25:56 +0200 Original-Received: from localhost ([::1]:33172 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1llaoV-00075V-41 for ged-emacs-devel@m.gmane-mx.org; Tue, 25 May 2021 13:25:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58448) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1llaU1-0004FR-TG for emacs-devel@gnu.org; Tue, 25 May 2021 13:04:45 -0400 Original-Received: from relay12.mail.gandi.net ([217.70.178.232]:39305) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1llaTx-0002mC-CF for emacs-devel@gnu.org; Tue, 25 May 2021 13:04:45 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 4320B20000A; Tue, 25 May 2021 17:04:35 +0000 (UTC) In-Reply-To: <87tumrgqrb.fsf@gmail.com> (=?iso-8859-1?Q?=22Jo=E3o_T=E1vora?= =?iso-8859-1?Q?=22's?= message of "Tue, 25 May 2021 09:30:00 +0100") Received-SPF: pass client-ip=217.70.178.232; envelope-from=juri@linkov.net; helo=relay12.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_H2=-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:269866 Archived-At: > I have no strong feelings on plist, versus alist, versus propertized > string, versus object, versus whatever. Just slightly strong feelings > as to the fundamental mission of this function which is to do > annotation/affixation/whatchacallit, not filtering or reordering. > > For reasons of "forward compatibility", as you called them, which is the > ability for newer backends to work on older Emacs that don't understand > these new things, if that work is done in `annotation-function` then it > needs to use propertized strings. But if it's done in a new thing, say > called decoration-function, it doesn't. As I said a month ago, while affixation-function was an improvement over annotation-function, it's still not perfect. I welcome a better API function, but OTOH adding prefix/suffix text properties on the annotation strings is not an improvement. > To clarify, the analog in some markup format is specifying something as > "emphasis" and then the renderer usually decides that bold if it can, or > surround it in asterisks. But the markup format doesn't usually say > "bold". For the same reasons, what you're now calling "columns" should > probably be referred to as "fields" or something equivalently agnostic > as to the format in which they are display. While looking for an analog, a better analogy would be the classic MVC architecture: - M: data comes from the list of completion strings; - V: render functions like completion--insert-* or icomplete-completions; - C: API callers that provide metadata functions that specify how to process data for displaying, e.g. they define display-sort-function where the prefix 'display-' hints that it affects the view, so the frontend has no own choice how to sort completions. Following such pattern, affixation-function could return more fields (e.g. when completions-format is customized to the value 'multi-column') in the same format as tabulated-list (and an indication in which column there are completion candidates) for the frontend to display in columns.