From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: carlmarcos--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#56171: Request for marking DEF entry when using completing-read Date: Fri, 24 Jun 2022 18:49:57 +0200 (CEST) Message-ID: References: <87v8sqqu0y.fsf@gnus.org-N5K4ctK----2> <87a6a2nkwh.fsf@gnus.org> Reply-To: carlmarcos@tutanota.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_579528_107969491.1656089397857" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29197"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , "56171@debbugs.gnu.org" <56171@debbugs.gnu.org> To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jun 24 18:54:58 2022 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 1o4maA-0007PW-2e for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 24 Jun 2022 18:54:58 +0200 Original-Received: from localhost ([::1]:40558 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o4ma5-00083d-Qy for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 24 Jun 2022 12:54:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58952) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o4mWM-0005c6-1P for bug-gnu-emacs@gnu.org; Fri, 24 Jun 2022 12:51:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49445) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o4mWL-0003fo-OL for bug-gnu-emacs@gnu.org; Fri, 24 Jun 2022 12:51:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o4mWL-0003Xu-N9 for bug-gnu-emacs@gnu.org; Fri, 24 Jun 2022 12:51:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: carlmarcos@tutanota.com Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 24 Jun 2022 16:51:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56171 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 56171-submit@debbugs.gnu.org id=B56171.165608940613543 (code B ref 56171); Fri, 24 Jun 2022 16:51:01 +0000 Original-Received: (at 56171) by debbugs.gnu.org; 24 Jun 2022 16:50:06 +0000 Original-Received: from localhost ([127.0.0.1]:43342 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o4mVR-0003WK-OT for submit@debbugs.gnu.org; Fri, 24 Jun 2022 12:50:06 -0400 Original-Received: from w1.tutanota.de ([81.3.6.162]:39072) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o4mVP-0003VD-S5 for 56171@debbugs.gnu.org; Fri, 24 Jun 2022 12:50:04 -0400 Original-Received: from w3.tutanota.de (unknown [192.168.1.164]) by w1.tutanota.de (Postfix) with ESMTP id D4703FBF811; Fri, 24 Jun 2022 16:49:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1656089397; s=s1; d=tutanota.com; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=hOEpklWPb5ozCdb+B2FwLEGqS5QKYE4rMk9p3IJNOJ4=; b=2G3kbr+q9tfUQT5250tZE2qdQEBmiUFoxdCz0d+7lfPuY362ymgojGhncG8sk9Y3 BwRshlIx0v3o4KRkAwPHbFI/trPz+MfU+ExY6LAqtVs9le6PGTtFq1tTeiDYw6gIZG7 6ISY0icuMQXmnk4+xuHnm8zowzaIdO57gw+MMhbeUd4uMFOqdIACbMVUSUQEff/8Aqh dVzntjOOjlDbeLJVZQLFD0HY+CLlgtv1oG00N7nO2/wvpacR88HgMCymj6TISxI4JGV Xa9gQk9AkWNjUlvPLaVoLXI8YsRMYRQhCFlh3dKrc84HPY7zA8TgmX2iLAWUW0mMxsN 7dJcMY/Zeg== 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:235204 Archived-At: ------=_Part_579528_107969491.1656089397857 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Jun 24, 2022, 16:14 by drew.adams@oracle.com: >> > It is a different thing than that. I customarily using the `up' and >> > `down' key to move through the collection of entries. Could there be >> > some form of indicator (e.g. highlight, underline, some other means) >> > that will tell me that is was selected as the default by the package >> > designer? Currently I see no distinction, with all entries in >> > collection as just an entry like any other. >> >> Again, what's the use case? Why do you want the default to be singled >> out in some way? >> > > I'm curious too. I don't say it couldn't be useful, > but I wonder what the aim is. > Wouldn't one normally associate a default with some sensible setting worth = looking into most times?=C2=A0 Perhaps this could be a user setting.=C2=A0=20 > BTW, note that the default value (or even any of a > list of default values) provided need not be among > the candidates for completion, if completion is lax > (REQUIRE-MATCH =3D nil). E.g.: > > (completing-read "q: " '("a" "b" "c" "d") > nil nil nil nil "e") > ------=_Part_579528_107969491.1656089397857 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Jun 24, 2022, 16:14 by drew.adams@oracle.com:
=
> It is a dif= ferent thing than that. I customarily using the `up' and
>= ; `down' key to move through the collection of entries. Could there be
=
> some form of indicator (e.g. highlight, underline, some oth= er means)
> that will tell me that is was selected as the = default by the package
> designer? Currently I see no dis= tinction, with all entries in
> collection as just an entr= y like any other.

Again, what's the use case? = Why do you want the default to be singled
out in some way?

I'm curious too. I don't say it c= ouldn't be useful,
but I wonder what the aim is.
Wouldn't one normally associate a default with = some sensible setting worth looking
into most ti= mes?  Perhaps this could be a user setting. 

BTW, not= e that the default value (or even any of a
list of default va= lues) provided need not be among
the candidates for completio= n, if completion is lax
(REQUIRE-MATCH =3D nil). E.g.:

(completing-read "q: " '("a" "b" "c" "d")
=
nil nil nil nil "e")

------=_Part_579528_107969491.1656089397857--