From: Achim Gratz <Stromeko@nexgo.de>
To: 16407@debbugs.gnu.org
Subject: bug#16407: Info-directory-list should always put this Emacs's info direc first
Date: Fri, 10 Jan 2014 20:47:26 +0100 [thread overview]
Message-ID: <87fvovpqk1.fsf@Rainer.invalid> (raw)
In-Reply-To: <d038kwjsn4.fsf@fencepost.gnu.org>
Glenn Morris writes:
> (And they could always do it with some site-specific elisp if they
> really wanted to. But I expect it to be very much a fringe case.)
I think you assume too much sophisication of a sysadmin who will
typically know little about the intricacies of Emacs. In any case, the
examples of site-lisp customization that I've been exposed to lately
have forced me to add "--no-site-lisp" to my all Emacs invocations.
> By default, Emacs uses the Gnus that comes with Emacs.
> To get it to use a different Gnus, you have to customize load-path.
> I do not think it unreasonable that you should have to similarly
> customize Info-directory-list to get the right manual.
The problem is that it's not immediately obvious when the two are not
kept in sync; something that presumably package manager should solve,
but doesn't. It would help if the built-in packages could be completely
deactivated upon installation of a different version of that same
package via package manager (that is, the custom-load and autoload stuff
for such a package delivered with Emacs should not be evaluated in that
case).
> I don't understand why it cannot be solved successfully by doing what I
> said. I don't care about seeing multiple versions of the manuals with
> the same name, I want to see only one version, and I want that version
> to be the version that comes with Emacs.
… while someone else might reaonably expect that he'll get the version
of the manual that he's installed first or last.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2014-01-10 19:47 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
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 [this message]
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
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=87fvovpqk1.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=16407@debbugs.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 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).