From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16407@debbugs.gnu.org
Subject: bug#16407: Info-directory-list should always put this Emacs's info direc first
Date: Fri, 10 Jan 2014 03:05:13 -0500 [thread overview]
Message-ID: <cxsisw45za.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <4s4n5cl20f.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 10 Jan 2014 02:38:56 -0500")
Glenn Morris wrote:
>> What if the user installs newer versions of, say, Gnus or Org from
>> their respective repositories?
>
> See my comment above.
> (Frankly, I suspect what happens at present in most such cases is that
> people install the lisp files in their load-path, but do not do anything
> with INFOPATH, so end up seeing the wrong Info pages anyway.)
PPS Actually, if they install via the Emacs package manager, there will
be no problem. That already does what I suggest: forces an entry on to
the very front of Info-directory-list. That would still come before the
element I am suggesting.
next prev parent reply other threads:[~2014-01-10 8:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 5:46 bug#16407: Info-directory-list should always put this Emacs's info direc first Glenn Morris
2014-01-10 7:16 ` Eli Zaretskii
2014-01-10 7:38 ` Glenn Morris
2014-01-10 7:44 ` Glenn Morris
2014-01-10 7:50 ` Glenn Morris
2014-01-10 8:07 ` Eli Zaretskii
2014-01-10 20:03 ` Glenn Morris
2014-01-10 8:09 ` Eli Zaretskii
2014-01-10 20:05 ` Glenn Morris
2014-01-10 20:20 ` Eli Zaretskii
2014-01-10 8:05 ` Glenn Morris [this message]
2014-01-10 8:21 ` Eli Zaretskii
2014-01-10 15:03 ` Stefan Monnier
2014-01-10 15:16 ` Eli Zaretskii
2014-01-10 16:36 ` Rüdiger Sonderfeld
2014-01-10 8:19 ` Eli Zaretskii
2014-01-10 20:11 ` Glenn Morris
2014-01-10 20:36 ` Eli Zaretskii
2014-01-10 21:03 ` Glenn Morris
2014-01-10 23:21 ` Glenn Morris
2014-01-10 20:54 ` Stefan Monnier
2014-01-10 19:47 ` Achim Gratz
2022-04-23 14:28 ` Lars Ingebrigtsen
2022-05-22 11:33 ` 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=cxsisw45za.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=16407@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.