From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stephen Berman <stephen.berman@gmx.net>,
stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: master ec9523a: Add a keybinding to the help menu to display manuals
Date: Fri, 16 Oct 2020 06:57:23 +0200 [thread overview]
Message-ID: <877drqu5sc.fsf@gnus.org> (raw)
In-Reply-To: <83o8l3y4ut.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 15 Oct 2020 16:51:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Alternatively, we could, of course, have a list of files in the
> package's main directory that need to be skipped when looking for the
> Info files (ChangeLog, COPYING, GNUmakefile, *.el, *.elc, etc.). But
> I think using a separate directory is much cleaner.
A blocklist of file names is probably the only realistic solution here,
considering how things look in the wild.
That is, this command should only list files that have ".info" in their
names somewhere, or have no suffix (except .gz) and not be in the
blocklist. So *.el etc in the blocklist shouldn't be necessary.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-16 4: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
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 [this message]
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=877drqu5sc.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.