From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Thibault Polge Newsgroups: gmane.emacs.bugs Subject: bug#59248: 29.0.50; apropos lists keywords as if they were variables Date: Sun, 13 Nov 2022 19:30:23 +0100 Message-ID: <87mt8upv0g.fsf@thb.lt> References: <87sfimpzdi.fsf@thb.lt> <835yfilo9k.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29085"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 59248@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Nov 13 19:39:44 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 1ouHtQ-0007Ky-4J for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 13 Nov 2022 19:39:44 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ouHst-0005vi-9q; Sun, 13 Nov 2022 13:39:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ouHsr-0005vR-NJ for bug-gnu-emacs@gnu.org; Sun, 13 Nov 2022 13:39:09 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ouHsk-0008L8-ED for bug-gnu-emacs@gnu.org; Sun, 13 Nov 2022 13:39:09 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ouHsk-0000Fc-6e for bug-gnu-emacs@gnu.org; Sun, 13 Nov 2022 13:39:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Thibault Polge Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 13 Nov 2022 18:39:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59248 X-GNU-PR-Package: emacs Original-Received: via spool by 59248-submit@debbugs.gnu.org id=B59248.1668364701898 (code B ref 59248); Sun, 13 Nov 2022 18:39:02 +0000 Original-Received: (at 59248) by debbugs.gnu.org; 13 Nov 2022 18:38:21 +0000 Original-Received: from localhost ([127.0.0.1]:48328 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ouHs5-0000EQ-4N for submit@debbugs.gnu.org; Sun, 13 Nov 2022 13:38:21 -0500 Original-Received: from 11.mo582.mail-out.ovh.net ([188.165.38.119]:39297) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ouHs2-0000ED-Ug for 59248@debbugs.gnu.org; Sun, 13 Nov 2022 13:38:20 -0500 Original-Received: from player693.ha.ovh.net (unknown [10.109.143.79]) by mo582.mail-out.ovh.net (Postfix) with ESMTP id E10EF22E68 for <59248@debbugs.gnu.org>; Sun, 13 Nov 2022 18:30:27 +0000 (UTC) Original-Received: from thb.lt (lfbn-idf3-1-593-4.w86-252.abo.wanadoo.fr [86.252.170.4]) (Authenticated sender: thibault@thb.lt) by player693.ha.ovh.net (Postfix) with ESMTPSA id 25C9130A1A611; Sun, 13 Nov 2022 18:30:24 +0000 (UTC) Authentication-Results: garm.ovh; auth=pass (GARM-103G0056be5234e-f7b2-407b-ba36-a0815829b5e0, CBDE94882D7934710CE3D53E3FCBD1D54B8ABCAA) smtp.auth=thibault@thb.lt X-OVh-ClientIp: 86.252.170.4 In-Reply-To: <835yfilo9k.fsf@gnu.org> X-Ovh-Tracer-Id: 4018055295521047372 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvgedrgedtgdduudehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvvefujghffffkgggtsehttdertddttddtnecuhfhrohhmpefvhhhisggruhhlthcurfholhhgvgcuoehthhhisggruhhlthesthhhsgdrlhhtqeenucggtffrrghtthgvrhhnpeeifeejhfehjeegjefhleeugeekveffvdelhfefvdfghfefjeevgeehveekheegfeenucfkphepuddvjedrtddrtddruddpkeeirddvhedvrddujedtrdegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepuddvjedrtddrtddruddpmhgrihhlfhhrohhmpeeothhhihgsrghulhhtsehthhgsrdhltheqpdhnsggprhgtphhtthhopedupdhrtghpthhtohepheelvdegkeesuggvsggsuhhgshdrghhnuhdrohhrghdpoffvtefjohhsthepmhhoheekvddpmhhouggvpehsmhhtphhouhht 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:247809 Archived-At: Eli Zaretskii writes: >> From: Thibault Polge >> Date: Sun, 13 Nov 2022 17:56:09 +0100 >> >> On a very recent (about yesterday) Emacs from HEAD, apropos lists >> interned keywords as undocumented variables. Eg, the following >> invocation: >> >> M-x apropos RET distant-foreground RET >> >> displays the following output: >> >> > Type RET on a type label to view its full documentation. >> > >> > :distant-foreground >> > Variable: (not documented) >> > Value: :distant-foreground >> >> This is technically correct --- keywords are variable-ish > > "M-x apropos" is not just about variables. It's about any symbol that > matches a regexp. In this case, the docstring for `apropos` is incorrect. It currently reads: "Show all meaningful Lisp symbols whose names match PATTERN. Symbols are shown if they are defined as functions, variables, or faces, or if they have nonempty property lists." The second sentence should include keywords. The produced output is also incorrect: a symbol is not a "Variable: (not documented)", and I'm not sure it makes sense to give its value, since it's auto-evaluating. >> but quite useless. At best, keywords just add noise to `apropos` >> output. At worst, they may be misleading, since an user may assume >> they can somehow control something by setq'ing a keyword. > > How can Emacs know that the user didn't actually _want_ to look up a > keyword? It is not impossible. I'm not sure I can think of a reason to do that: all the user would learn is that something, somewhere, interned that keyword. But maybe there are use cases that escape me.