all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Weiner <rsw@gnu.org>
To: James Cloos <cloos@jhcloos.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Alex Dunn <dunn.alex@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: why is site-lisp placed before the default load path?
Date: Tue, 2 Aug 2016 16:47:58 -0400	[thread overview]
Message-ID: <CA+OMD9jKHmDZB-1KywF95e2-=aSru=FN5=017Lb0SeKdav9SZQ@mail.gmail.com> (raw)
In-Reply-To: <m3bn1bx7d4.fsf@carbon.jhcloos.org>

[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]

On Tue, Aug 2, 2016 at 4:07 PM, James Cloos <cloos@jhcloos.com> wrote:

> >>>>> "RW" == Robert Weiner <rsw@gnu.org> writes:
>
> RW> ​If a package unintentionally shadows/overrides a standard/core Emacs
> RW> library, then it is the package that is broken and needs to be fixed.
> If
> RW> instead the behavior is intentional then that is what the current
> load-path
> RW> order is designed to allow.
>
> The point is that if sub directories are nto automatically included, it is
> easier to  manage things.  Especially when using one's dist's packaging.
>

​I can see where you might have test subdirectories or others that you
would not want included in load-path.  If you want to justify a change
though, you should give one or more clear examples of where the default
behavior is the major cause of a problem.
​


>
> I had to make substantial changes to my .emacs when the auto sub dirs
> was added to fix all of the damage that caused.


​Be explicit.  Don't just say damage.  Give precise examples of what
happened and what was required to fix it so everyone can understand what
you are talking​

​about.

Bob
​

[-- Attachment #2: Type: text/html, Size: 2573 bytes --]

  reply	other threads:[~2016-08-02 20:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 16:24 why is site-lisp placed before the default load path? Alex Dunn
2016-08-01 16:39 ` Eli Zaretskii
2016-08-01 17:19   ` Alex Dunn
2016-08-01 17:54     ` Robert Weiner
2016-08-01 18:15       ` Alex Dunn
2016-08-02 17:35         ` James Cloos
2016-08-02 18:35           ` Robert Weiner
2016-08-02 20:07             ` James Cloos
2016-08-02 20:47               ` Robert Weiner [this message]
2016-08-02  0:25       ` Clément Pit--Claudel
2016-08-02 14:58       ` Stefan Monnier

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='CA+OMD9jKHmDZB-1KywF95e2-=aSru=FN5=017Lb0SeKdav9SZQ@mail.gmail.com' \
    --to=rsw@gnu.org \
    --cc=cloos@jhcloos.com \
    --cc=dunn.alex@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rswgnu@gmail.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 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.