From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Kangas <stefankangas@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: master ec9523a: Add a keybinding to the help menu to display manuals
Date: Thu, 15 Oct 2020 11:00:58 +0200 [thread overview]
Message-ID: <87blh3rhh1.fsf@gmx.net> (raw)
In-Reply-To: <2B40CB5F-0EDB-4909-9A21-395C9A3B0218@gnu.org> (Eli Zaretskii's message of "Thu, 15 Oct 2020 10:43:44 +0300")
On Thu, 15 Oct 2020 10:43:44 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
> On October 15, 2020 10:00:12 AM GMT+03:00, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>> >> files under info/ end in ".info". Are there known cases of
>> >> extensionless info files that do not correspond to a file ending in
>> >> ".info" or ".info.gz" (or another compression suffix)? If not,
>> then
>> >> removing that bit of the code will prevent the current false
>> positives.
>> >
>> > It used to be common to have Info files with names like `foo`,
>> `foo-1`,
>> > `foo-2`, ... Splitting Info files has gotten out of fashion due to
>> the
>> > growing size of RAM, and the use of a `.info` extension has grown
>> > a lot too. Maybe we could start assuming that all those files
>> nowadays
>> > have a `.info` extension?
>>
>> I had a look in
>>
>> /usr/share/info/
>>
>> here, and it looks like they all have .info in their names.
>
> I have in my /usr/share/info gobs of old Info files without any extension. So
> please let's not make any changes that would exclude them from completion by
> this command.
>
> If someone has files in Info-related directories that are not Info files, they
> should get their act together. And if we do that on ELPA, let's get our act
> together, instead of making breaking changes like that.
According to (info "(elisp) Multi-file Packages"), it seems that the
package library currently does not support a separate info directory
within the package directory:
"If the content directory contains a file named ‘dir’, this is assumed
to be an Info directory file made with ‘install-info’. *Note Invoking
install-info: (texinfo)Invoking install-info. The relevant Info files
should also be present in the content directory. In this case, Emacs
will automatically add the content directory to ‘Info-directory-list’
when the package is activated."
I haven't looked at the code so I don't know how feasible it is for ELPA
to accommodate a separate info directory.
Steve Berman
next prev parent reply other threads:[~2020-10-15 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201013010930.20500.91773@vcs0.savannah.gnu.org>
[not found] ` <20201013010931.ABE62209AA@vcs0.savannah.gnu.org>
2020-10-14 19:06 ` master ec9523a: Add a keybinding to the help menu to display manuals Stefan Kangas
2020-10-14 22:33 ` Stephen Berman
2020-10-15 1:57 ` Stefan Monnier
2020-10-15 7:00 ` Lars Ingebrigtsen
2020-10-15 7:34 ` Stephen Berman
2020-10-15 7:43 ` Eli Zaretskii
2020-10-15 9:00 ` Stephen Berman [this message]
2020-10-15 13:51 ` Eli Zaretskii
2020-10-16 4:08 ` Richard Stallman
2020-10-16 6:10 ` Eli Zaretskii
2020-10-18 4:10 ` Richard Stallman
2020-10-18 14:35 ` Eli Zaretskii
2020-10-19 3:48 ` Richard Stallman
2020-10-16 4:57 ` Lars Ingebrigtsen
2020-10-15 6:55 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blh3rhh1.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).