From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jeremy Bryant Newsgroups: gmane.emacs.devel Subject: Improving info-look.el for (c) -was- Re: [ELPA] New package c-intro-and-ref -- was Re: Proposal: Include C Manual from RMS in Emacs git, and/or release Date: Sat, 07 Dec 2024 13:30:10 +0000 Message-ID: <87ed2j8vtp.fsf@jeremybryant.net> References: <87ser8c230.fsf@jeremybryant.net> <86ser87rut.fsf@gnu.org> <86cyia4503.fsf@gnu.org> <87bjxsbc8h.fsf@jeremybryant.net> <86a5db1vc6.fsf@gnu.org> <8734j3awd7.fsf@jeremybryant.net> <865xnyznre.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="16780"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org, philipk@posteo.net, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 07 14:31:15 2024 Return-path: Envelope-to: ged-emacs-devel@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 1tJutr-00047Y-Fp for ged-emacs-devel@m.gmane-mx.org; Sat, 07 Dec 2024 14:31:14 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tJutG-0000XM-Fe; Sat, 07 Dec 2024 08:30:34 -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 1tJutC-0000Wz-EX for emacs-devel@gnu.org; Sat, 07 Dec 2024 08:30:30 -0500 Original-Received: from out-184.mta0.migadu.com ([2001:41d0:1004:224b::b8]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tJut7-0003JC-Ot for emacs-devel@gnu.org; Sat, 07 Dec 2024 08:30:29 -0500 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeremybryant.net; s=key1; t=1733578213; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=C/o/mkOQ+eB+Jqx9jSlIYN/UaYmadkX/KYrp18CJzbY=; b=cv2YHFlLB7Ak/8TW0VUB1bKfuN0cVOJN3acVvRATjcLiUwcmHayNd7wAVA00rqqtV9hmxg R2wXIFnFdG513PhhE1VfiNVhGr/OHMufK5QjaO3kK9iaCrak4UWHZbZI0uGCUzWmkFRxWr wpBGheunClfr6g4+aN5yVwy7wWKr2z3weOjuWOvD6fzXtTcWOfCxGN1K60clTyW6YivrZa WhNQAEO+HIsvWBDwkIxti+UYSC8oLvsPOzCdafVt7AN+jnK/TeRlWY5ABamAXHsU1JiPoO pS9xPBE4VAACx7qUHA/ujaXEWXkumQ/o9FK2NanSY/GYbO4cXsO7MGqyz8sBvQ== In-Reply-To: <865xnyznre.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 05 Dec 2024 07:45:25 +0200") X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:1004:224b::b8; envelope-from=jb@jeremybryant.net; helo=out-184.mta0.migadu.com X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:326165 Archived-At: Eli Zaretskii writes: >> From: Jeremy Bryant >> >From a complementary point of view, reading this list it appears that >> there is a smaller number of C contributors to Emacs, compared to Lisp, >> and more C contributors are needed to work on Emacs. >> >> Can we facilitate C documentation? >> For example. The info-look.el subsystem already adds lookup >> facility for manuals such >> as (libc). Wouldn't it be useful to also have c.info similarly >> available and to aid in Emacs C development? That is >> part of the motivation. > > It's okay to extend info-look.el to use this manual (and perhaps also > the sibling GNU C manual?), but please note that we do NOT provide the > glibc Info manual on ELPA, although it is referenced by info-look.el > (and I personally have that manual installed on my system, even though > my main development machine doesn't use glibc). > Okay, on this particular change, after studying info-look.el, it is not clear to me how info-look resolves multiple manuals, in order to make it work with both (libc), (c) and other manuals on the same buffer. Should we add another info-lookup-maybe-add-help, or amend the existing one? Would you have suggestions on how to work on this, so I can experiment with a patch?