From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Protesilaos Stavrou Newsgroups: gmane.emacs.devel Subject: Re: on helm substantial differences Date: Tue, 17 Nov 2020 14:06:12 +0200 Message-ID: <87ima45gsr.fsf@protesilaos.com> References: <87wnymda5g.fsf@mail.linkov.net> <83a6vhth3z.fsf@gnu.org> <87zh3h2fx9.fsf@mail.linkov.net> <871rgtndph.fsf@mail.linkov.net> <3c9e3ebc-1ff6-402e-8e87-cc9b5f19a1fc@default> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18248"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: spacibba@aol.com, bugs@gnu.support, andreyk.mad@gmail.com, emacs-devel@gnu.org, rudalics@gmx.at, monnier@iro.umontreal.ca, ghe@sdf.org, Eli Zaretskii , Juri Linkov To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 17 13:07:14 2020 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 1kezlS-0004ei-0X for ged-emacs-devel@m.gmane-mx.org; Tue, 17 Nov 2020 13:07:14 +0100 Original-Received: from localhost ([::1]:49482 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kezlR-00075h-0T for ged-emacs-devel@m.gmane-mx.org; Tue, 17 Nov 2020 07:07:13 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56142) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kezkn-0006G7-Ql for emacs-devel@gnu.org; Tue, 17 Nov 2020 07:06:34 -0500 Original-Received: from relay9-d.mail.gandi.net ([217.70.183.199]:33913) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kezkj-0007Nc-Lx; Tue, 17 Nov 2020 07:06:32 -0500 X-Originating-IP: 94.46.225.161 Original-Received: from kronos (unknown [94.46.225.161]) (Authenticated sender: public@protesilaos.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id F058BFF809; Tue, 17 Nov 2020 12:06:17 +0000 (UTC) In-Reply-To: <3c9e3ebc-1ff6-402e-8e87-cc9b5f19a1fc@default> (Drew Adams's message of "Mon, 16 Nov 2020 16:04:30 -0800 (PST)") Received-SPF: none client-ip=217.70.183.199; envelope-from=info@protesilaos.com; helo=relay9-d.mail.gandi.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/17 07:06:25 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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:259285 Archived-At: On 2020-11-16, 16:04 -0800, Drew Adams wrote: >> >> Like there are already possible choices 'horizontal' and 'vertical' >> >> in the user option 'completions-format', it could also support >> >> a new choice like 'rich'. >> > >> > `rich' is a poor choice, IMO - it doesn't mean much. >> >> This is a reference to the package ivy-rich > > Is it? What says that? > > The name itself doesn't say that. If that's important > then call it `ivy-rich', not `rich'. But that just > punts, no? Then someone needs to find that package > and see what it says "rich" means here. > > Just because some other package uses a vague name like > that, does that mean Emacs shouldn't do better? > > Might as well call it `enhanced', `special', `super', > or `wonderful'. Does "rich" have a meaning that > suggests something here other than "full" or "great"? What 'ivy-rich' does is complement the candidates of 'ivy-mode' with pertinent information. For example, standard Ivy shows a vertical list consisting only of buffer names, while 'ivy-rich' adds to them their major mode and file system path, filling up the empty space. Couched in those terms, "rich" could be replaced with something like "detailed", "descriptive", "informative"... Or, if you want to be precise, prepend "vertical-" to those options. -- Protesilaos Stavrou protesilaos.com