From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Michael Welsh Duggan Newsgroups: gmane.emacs.devel Subject: Re: Some ideas with Emacs Date: Sun, 01 Dec 2019 14:44:48 -0500 Message-ID: <87sgm3akzz.fsf@md5i.com> References: <837e3iq0ks.fsf@gnu.org> <87h82my0fm.fsf@gmx.de> <4f3fe5b0-3a63-346e-5cea-bb5ed057e028@gmail.com> <83o8wtond2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="60782"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 01 20:45:06 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 1ibV9V-000FeL-Mi for ged-emacs-devel@m.gmane.org; Sun, 01 Dec 2019 20:45:06 +0100 Original-Received: from localhost ([::1]:54844 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibV9T-0003PI-Sp for ged-emacs-devel@m.gmane.org; Sun, 01 Dec 2019 14:45:03 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37698) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibV9H-0003Ox-77 for emacs-devel@gnu.org; Sun, 01 Dec 2019 14:44:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ibV9G-0003v6-39 for emacs-devel@gnu.org; Sun, 01 Dec 2019 14:44:51 -0500 Original-Received: from md5i.com ([75.151.244.229]:34156) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ibV9F-0003us-Rg for emacs-devel@gnu.org; Sun, 01 Dec 2019 14:44:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=md5i.com; s=dkim; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:To:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=R561Qmx+HPisX+AsJ/GpFpZMOaqpvHQtBDSMYjffY4Y=; b=S1W6embajQQ7fBETuk+gMBwuMC X0Ty5jTdbtk1cjILlZXqmfh44HwefWBB6XPUrt3BYp03FGy6OhbRXf7FG4ALBzsaFhLUYhxo4nlTg Eze6IYLJHQpzG0TOrCvLZ90fW; Original-Received: from md5i by md5i.com with local (Exim 4.93-RC4) (envelope-from ) id 1ibV9E-0002QG-JS for emacs-devel@gnu.org; Sun, 01 Dec 2019 14:44:48 -0500 In-Reply-To: <83o8wtond2.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Nov 2019 09:05:29 +0200") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 75.151.244.229 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:242969 Archived-At: Eli Zaretskii writes: >> Cc: Eli Zaretskii , Stefan Kangas , >> Anonymous , Emacs developers >> From: Cl=E9ment Pit-Claudel >> Date: Fri, 29 Nov 2019 16:42:28 -0500 >>=20 >> would be great would be if there were links to the manual from the >> docstrings for functions that are covered in both. > > 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'). I'm not in a position where I could write this myself, but I thought I'd throw the idea out there in case someone else is interested in writing such a thing. --=20 Michael Welsh Duggan (md5i@md5i.com)