From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Kangas <stefankangas@gmail.com>,
emacs-devel@gnu.org
Subject: Re: master ec9523a: Add a keybinding to the help menu to display manuals
Date: Wed, 14 Oct 2020 21:57:10 -0400 [thread overview]
Message-ID: <jwv4kmw1cgb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k0vs4eun.fsf@rub.de> (Stephen Berman's message of "Thu, 15 Oct 2020 00:33:52 +0200")
> 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?
Stefan
next prev parent reply other threads:[~2020-10-15 1:57 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv4kmw1cgb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=stefankangas@gmail.com \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.