From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Some ideas with Emacs Date: Sun, 01 Dec 2019 22:48:22 +0200 Message-ID: <83a78bn561.fsf@gnu.org> References: <837e3iq0ks.fsf@gnu.org> <87h82my0fm.fsf@gmx.de> <4f3fe5b0-3a63-346e-5cea-bb5ed057e028@gmail.com> <83o8wtond2.fsf@gnu.org> <87sgm3akzz.fsf@md5i.com> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="50332"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Michael Welsh Duggan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 01 21:48:49 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ibW9B-000Cu1-EJ for ged-emacs-devel@m.gmane.org; Sun, 01 Dec 2019 21:48:49 +0100 Original-Received: from localhost ([::1]:55392 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibW94-0002cV-NE for ged-emacs-devel@m.gmane.org; Sun, 01 Dec 2019 15:48:42 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46995) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibW8y-0002cK-AO for emacs-devel@gnu.org; Sun, 01 Dec 2019 15:48:37 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53156) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ibW8y-0004Re-5I; Sun, 01 Dec 2019 15:48:36 -0500 Original-Received: from [176.228.60.248] (port=4928 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ibW8x-0004gE-8F; Sun, 01 Dec 2019 15:48:35 -0500 In-reply-to: <87sgm3akzz.fsf@md5i.com> (message from Michael Welsh Duggan on Sun, 01 Dec 2019 14:44:48 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:242970 Archived-At: > From: Michael Welsh Duggan > Date: Sun, 01 Dec 2019 14:44:48 -0500 > > > Almost all of them are, so it would be a significant bloat of the > > Emacs's memory footprint for very little gain. I suggest that you > > instead teach yourself to use "C-h S" every time you wonder whether a > > function or variable is described in the manual(s): this command > > sounds like exactly what you'd want. (If you already use it, I guess > > I don't understand what would you gain by having the information in > > the doc string.) > > Although not trivial to write, this might be able to be auto-generated > to some extent. If the function being looked up is an internal function > or the file in which the function is implemented is in the emacs > installed lisp files location (usually > $prefix/share/emacs/$VERSION/lisp), then we could look up the function > in them emacs-lisp manual and, if found, we could add a link to that > entry. This could be implemented in the > `help-fns-describe-function-functions' hook. The manual look-up would > be a hacked up version of `Info-index` which requires an exact match. > Something similar would be done for variable look-up (in > `help-fns-describe-variable-functions'). Isn't that what "C-h S" already does?