From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, 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: Sun, 18 Oct 2020 17:35:59 +0300 [thread overview]
Message-ID: <83d01fsisw.fsf@gnu.org> (raw)
In-Reply-To: <E1kU01Z-0008R1-FE@fencepost.gnu.org> (message from Richard Stallman on Sun, 18 Oct 2020 00:10:25 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: larsi@gnus.org, stephen.berman@gmx.net, stefankangas@gmail.com,
> emacs-devel@gnu.org
> Date: Sun, 18 Oct 2020 00:10:25 -0400
>
> > It is not a catastrophe not to move the files physically -- they come
> > with a DIR file of their own, and thus can be added to the Info
> > directory list -- but the problem is that they are mixed with many
> > non-Info files, and that violates the expectations of Info readers.
>
> How about making an 'info' subdirectory in the package
> and putting the info files there?
That'd be ideal, but AFAIU there were reasons why ELPA didn't go for
that structure.
next prev parent reply other threads:[~2020-10-18 14:35 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 [this message]
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=83d01fsisw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@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.