From: Achim Gratz <Stromeko@nexgo.de>
To: 14513@debbugs.gnu.org
Subject: bug#14513: 24.3.50; Site load-path pieces differ in MSYS build
Date: Fri, 31 May 2013 21:01:32 +0200 [thread overview]
Message-ID: <8761xzgeib.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAPM58oisF_66DboK2hajGjC4kJ43SqLXqZg2svsizJ7Qpi7oow@mail.gmail.com>
Eli Zaretskii writes:
> Well, then just don't do that. Don't unpack each version into a
> separate directory. That's what this change was all about.
I have no dogs in this race. On the two Windows systems that I care
about I have full administrative priviledges and can install (and
re-install) things exactly the way I want them. I'll reiterate that
(just as on UN*X) many users are at the mercy of whoever administrates
their system and such changes often take a long time to trickle through
to these people (they may not understand what Emacs is, much less care
about site-lisp). If this is at least documented clearly (not just that
this change is made, but _how_ to install things differently now) then
some churn can perhaps be avoided by having something to point to.
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:[~2013-05-31 19:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 13:46 bug#14513: 24.3.50; Site load-path pieces differ in MSYS build Richard Copley
2013-05-30 16:40 ` Eli Zaretskii
2013-05-30 17:56 ` Richard Copley
2013-05-30 18:20 ` Eli Zaretskii
2013-05-30 19:02 ` Achim Gratz
2013-05-30 19:16 ` Eli Zaretskii
2013-05-30 19:57 ` Achim Gratz
2013-05-30 20:39 ` Eli Zaretskii
2013-05-30 21:21 ` Stefan Monnier
2013-05-31 19:01 ` Achim Gratz [this message]
2013-05-31 19:24 ` Eli Zaretskii
2013-05-30 19:06 ` Stefan Monnier
2013-05-30 19:18 ` Eli Zaretskii
2013-05-30 19:20 ` Richard Copley
[not found] ` <CAPM58ojwzkw8kxKc8P4G0mdsJgmYmo-ZxSbcN1F2J+QVyFaHMw@mail.gmail.com>
2013-05-30 19:29 ` Eli Zaretskii
2013-05-30 20:00 ` Stefan Monnier
2013-05-30 20:42 ` Eli Zaretskii
2013-05-30 21:43 ` Stefan Monnier
2013-05-31 6:20 ` Eli Zaretskii
2013-05-31 9:52 ` Richard Copley
2013-05-31 11:35 ` Eli Zaretskii
2013-05-31 12:55 ` Richard Copley
2013-06-01 16:04 ` Richard Copley
2013-06-01 16:38 ` Eli Zaretskii
2013-06-01 17:06 ` Richard Copley
[not found] ` <CAPM58og6ySbmR28vQH+m7dp-zYgVwrrYqthO6_ZfGodV9Si23w@mail.gmail.com>
[not found] ` <8361xx20lb.fsf@gnu.org>
2013-06-01 18:00 ` Richard Copley
2013-06-02 11:33 ` Richard Copley
2013-06-04 18:27 ` Richard Copley
2013-06-04 19:37 ` Eli Zaretskii
2013-06-04 20:14 ` Richard Copley
2013-06-04 20:21 ` Glenn Morris
2013-06-07 8:14 ` Eli Zaretskii
2013-06-07 17:48 ` Richard Copley
2013-06-04 23:55 ` Juanma Barranquero
2013-06-06 15:37 ` Eli Zaretskii
2013-06-07 1:49 ` Juanma Barranquero
2013-06-07 6:51 ` Eli Zaretskii
[not found] ` <83ip20469l.fsf@gnu.org>
2013-05-30 19:29 ` bug#14514: Fwd: " Richard Copley
2013-05-30 19:49 ` bug#14513: " Richard Copley
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=8761xzgeib.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=14513@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).