unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Warning (initialization): Your `load-path' seems to contain
Date: Wed, 18 Jun 2014 20:58:19 +0800	[thread overview]
Message-ID: <8761jytlw4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87ppi61o2x.fsf@skimble.plus.com

Sharon Kimble <boudiccas@skimble.plus.com> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Ruben Maher <eqyiel@gmail.com> writes:
>>
>>> Sharon Kimble <boudiccas@skimble.plus.com> writes:
>>>
>>>> For some time now I've been getting this -
>>>> Warning (initialization): Your `load-path' seems to contain
>>>> your `.emacs.d' directory: /home/boudiccas/.emacs.d/
>>>> This is likely to cause problems...
>>>> Consider using a subdirectory instead, e.g.: /home/boudiccas/.emacs.d/lisp
>>>> in my *Warnings* buffer.
>>>>
>>>> These are the relevant lines from my "init.el"
>>>> (setq load-path (cons "/home/boudiccas/.emacs.d/lisp" load-path))
>>>> (add-to-list 'load-path "/home/boudiccas/.emacs.d/personal-lisp")
>>>>
>>>> Why doesn't it accept what's in the "init.el" please, and what can I
>>>> do to put it right?
>>>
>>> Hi Sharon,
>>>
>>> Emacs is not rejecting init.el, it's just warning you.  If you don't
>>> want to see the warning anymore you can drop this snippet in there:
>>>
>>> (eval-after-load "warnings"
>>>   ;; shut up, emacs!
>>>   '(setq display-warning-minimum-level :error))
>>>
>>> Kind regards,
>>>
>>> Ruben
>>
>> But the root cause still ought to be that, somewhere in your init,
>> you've got (add-to-list 'load-path "/home/boudiccas/.emacs.d"). Are you
>> sure you don't? I've been following emacs trunk, and a while ago got the
>> same warning.
>>
>> I fixed it by removing ~/.emacs.d from my load path, putting
>> (add-to-list 'load-path "~/.emacs.d/lisp") in my ~/.emacs.d/init.el
>> file, and then putting everything I wanted to require or load underneath
>> ~/.emacs.d/lisp. No warnings anymore...
>>
> Thanks for this Eric, this is what I ended up doing, although I was
> very wary of destroying my hard-won set-up, and I did restore my
> "init.el" from backup as it was so cobbled about that I couldn't see
> what was loading and what wasn't! And I did have 2 instances of
> (add-to-list 'load-path "~/.emacs.d") which were soon commented out!
> That problem of "Warning (initialization)" has been bugging me for
> months and I kept putting off dealing with it but it got embarrassing
> when the task had been repeated for 84 days, and still not dealt
> with! :)

I like that about Org: it embarrasses you, but gently :)

I was also very wary of messing with my init-file setup, but I was
pleased with how easy it turned out to be. And the resulting arrangement
has the advantage of being easier to manage when you need to comment
things out, or track down the exact source of an error. Glad to hear
it's all working well!

> But now its all pristine clean and working well, thanks folks :)
>
> Sharon.




      reply	other threads:[~2014-06-18 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 18:14 Warning (initialization): Your `load-path' seems to contain Sharon Kimble
2014-06-18  4:42 ` Ruben Maher
2014-06-18  5:17   ` Eric Abrahamsen
2014-06-18 10:58     ` Sharon Kimble
2014-06-18 12:58       ` Eric Abrahamsen [this message]

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=8761jytlw4.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=help-gnu-emacs@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.
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).