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 17:20:20 -0500 Message-ID: <87mucbadsr.fsf@md5i.com> References: <837e3iq0ks.fsf@gnu.org> <87h82my0fm.fsf@gmx.de> <4f3fe5b0-3a63-346e-5cea-bb5ed057e028@gmail.com> <83o8wtond2.fsf@gnu.org> <87sgm3akzz.fsf@md5i.com> <83a78bn561.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="146100"; 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 23:20:40 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 1ibXa3-000bsE-Ne for ged-emacs-devel@m.gmane.org; Sun, 01 Dec 2019 23:20:40 +0100 Original-Received: from localhost ([::1]:56204 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibXa1-0008Vc-TV for ged-emacs-devel@m.gmane.org; Sun, 01 Dec 2019 17:20:37 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59228) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibXZn-0008Uw-6d for emacs-devel@gnu.org; Sun, 01 Dec 2019 17:20:24 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ibXZm-00013a-1C for emacs-devel@gnu.org; Sun, 01 Dec 2019 17:20:23 -0500 Original-Received: from md5i.com ([75.151.244.229]:34914) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ibXZl-00013D-Q4 for emacs-devel@gnu.org; Sun, 01 Dec 2019 17:20:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=md5i.com; s=dkim; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References: Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=+PaQMn6DNbN1hkVDDh5tWgVW4Wc9NCs0Plzasww2loY=; b=jkt6nZtWqO8gKHP613GAF6N3Zu T2MtXh1ZdhQWnzO62d2mMt4TydufUF3jW0AADuu+/KWtTbPkJeK/spK4M0Bvq/h8lkNNAgzFw4bPc fv71Qc2Xq4fhnMMHQ5c22YYES; Original-Received: from md5i by md5i.com with local (Exim 4.93-RC4) (envelope-from ) id 1ibXZk-0006xE-Oh for emacs-devel@gnu.org; Sun, 01 Dec 2019 17:20:20 -0500 In-Reply-To: <83a78bn561.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 01 Dec 2019 22:48:22 +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:242972 Archived-At: Eli Zaretskii writes: >> 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? It appears to, indeed. All that is needed, then, is to integrate this as a hyperlink into the C-h [f,v] buffers, without asking initially what type of symbol you're looking for. -- Michael Welsh Duggan (md5i@md5i.com)