From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 11959@debbugs.gnu.org
Subject: bug#11959: 24.1.50; Warning: Lisp directory `C:/Emacs-24-2012-07-16/../site-lisp' does not exist.
Date: Wed, 18 Jul 2012 20:08:01 +0300 [thread overview]
Message-ID: <834np59evi.fsf@gnu.org> (raw)
In-Reply-To: <BEC88BE3713A414E88134D749C25AEA0@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <11959@debbugs.gnu.org>
> Date: Wed, 18 Jul 2012 08:20:15 -0700
>
> > The other part of the puzzle is that when Emacs on Windows starts, it
> > always defines EMACSLOADPATH and puts 2 site-lisp directories into it:
> > one that is in the same tree as the binary, which is supposed to be
> > version dependent, and another one that is a sibling of the root of
> > the installed tree, which is supposed to be version-independent.
>
> You mean that it does so systematically, in a hard-coded fashion? Or does it
> put those there only if such directories exist?
On Windows, there's no test for their existence.
> > And if we do want to check that, why not exempt the site-lisp
> > directories from the need to exist, like we do in the case where
> > EMACSLOADPATH is not set?
>
> Such exceptionalism smacks of fragile design. What applies to site-lisp might
> apply to some other directory as well (tomorrow, if not today).
Not exactly. The other directories, 'lisp' and 'leim', are _required_
by Emacs, otherwise it's an incomplete package, i.e. a broken
installation. By contrast, 'site-lisp' is not required for Emacs
operation, it's a convenience for the user to put her local stuff in.
On Unix, Emacs always tested whether site-lisp exists before adding it
to load-path, with the rationale that it's not required.
next prev parent reply other threads:[~2012-07-18 17:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 16:40 bug#11959: 24.1.50; Warning: Lisp directory `C:/Emacs-24-2012-07-16/../site-lisp' does not exist Drew Adams
2012-07-17 17:40 ` Eli Zaretskii
2012-07-17 17:42 ` Drew Adams
2012-07-18 14:57 ` Eli Zaretskii
2012-07-18 15:20 ` Drew Adams
2012-07-18 17:08 ` Eli Zaretskii [this message]
2012-07-29 23:50 ` Glenn Morris
2012-07-29 23:58 ` Glenn Morris
2012-07-30 3:34 ` Eli Zaretskii
2012-07-30 6:05 ` Jan Djärv
2012-07-30 13:30 ` Eli Zaretskii
2012-07-30 6:43 ` Glenn Morris
2012-07-30 13:32 ` Eli Zaretskii
2012-07-30 15:09 ` Glenn Morris
2012-07-30 15:11 ` Glenn Morris
2012-07-31 17:10 ` Eli Zaretskii
2012-08-01 20:32 ` Stefan Monnier
2012-08-02 15:29 ` Eli Zaretskii
2012-08-02 15:42 ` Glenn Morris
2012-08-04 14:30 ` Eli Zaretskii
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=834np59evi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11959@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).