Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setting $HOME/.emacs.d/ in the load-path causes initialization warning. #49

Closed
wallacewinfrey opened this issue Mar 4, 2014 · 3 comments

Comments

@wallacewinfrey
Copy link

If one follows the [installation instructions](git clone http://github.com/eschulte/emacs24-starter-kit.git), upon startup an initialization warning is generated, stating:

Warning (initialization): Your `load-path' seems to contain
your `.emacs.d' directory: /home/user/.emacs.d/
This is likely to cause problems...
Consider using a subdirectory instead, e.g.: /home/user/.emacs.d/lisp

Not a huge issue for sure, but one that's likely to confuse a new user...
System details, if you need them...

% apt-cache show emacs-snapshot | grep Version
Version: 2:20140101-1~ppa1~saucy1
% cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION="Ubuntu 13.10"
% dpkg-query -l | grep emacs | sed -e 's/ \+/ /g' | cut -d' ' -f2 | tr '\n' ' '
emacs-snapshot emacs-snapshot-bin-common emacs-snapshot-common emacs-snapshot-el emacs-snapshot-gtk emacsen-common
@eschulte
Copy link
Owner

eschulte commented Mar 5, 2014

Yes, that certainly could be confusing (and I'm seeing that behavior now too). I'm disinclined to remove .emacs.d/ from the load path, as many people may now be relying on it's presence. I'll look into silencing the warning...

@gugek
Copy link

gugek commented Mar 7, 2014

I saw this in a 24.4 build so this is new behavior.

@eschulte
Copy link
Owner

Alright. Having thought about this, I've now removed ~/.emacs.d/ from the load path, as ~/.emacs.d/src/ should be used for source files. See a0e81cb. Hopefully this doesn't affect too many people.

Thanks for bringing this to my attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants