all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
To: David Caldwell <david@porkrind.org>
Cc: 19850@debbugs.gnu.org
Subject: bug#19850: 25.0.50; [PATCH] configure.ac: Fix site-lisp paths with NS self-contained apps.
Date: Sat, 14 Feb 2015 10:25:34 +0100	[thread overview]
Message-ID: <B706CA02-D0A8-4715-A2BB-2BC35A43A77C@swipnet.se> (raw)
In-Reply-To: <54DE5368.7020009@porkrind.org>


> 13 feb 2015 kl. 20:41 skrev David Caldwell <david@porkrind.org>:
> 
> On 2/13/15 5:41 AM, Jan D. wrote:
>> 
>> 
>> That's not the point.  The point is that the Emacs I compile for myself
>> should by default ignore site wide stuff in global places.
> 
> Then wouldn't it act differently than the Linux version? Don't you get
> "/usr/local/emacs/site-lisp" by default there? "/Library" is the
> equivalent of "/usr/local" on OS X ("/System/Library" would be "/usr").

Yes, I get /usr/local/emacs/site-lisp by default, which is different from the system site-lisp, which is in /usr/share/emacs.
So it takes effort to get your self-built emacs to use the system site-lisp.

Also, /Library is in not the equivalent of /usr/local.  /usr/local is the equivalent of /usr/local.
/Library is a system directory, a mix of /etc and /usr/share.  There are startup daemons there, fonts, internet plugins and so on.  These things are not in /usr/local on any sane Unix-like OS.

	Jan D.






  reply	other threads:[~2015-02-14  9:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 21:51 bug#19850: 25.0.50; [PATCH] configure.ac: Fix site-lisp paths with NS self-contained apps David Caldwell
2015-02-13  6:57 ` Jan D.
2015-02-13  7:28   ` David Caldwell
2015-02-13 13:41     ` Jan D.
2015-02-13 19:41       ` David Caldwell
2015-02-14  9:25         ` Jan D. [this message]
2015-02-14 10:09           ` David Caldwell
2015-02-13 16:36     ` Jan D.
2015-02-13 16:46     ` Jan D.

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=B706CA02-D0A8-4715-A2BB-2BC35A43A77C@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=19850@debbugs.gnu.org \
    --cc=david@porkrind.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.