From: Lele Gaifax <lele@metapensiero.it>
To: help-gnu-emacs@gnu.org
Subject: Initialization warning with latest emacs snapshot
Date: Tue, 03 Dec 2013 22:08:50 +0100 [thread overview]
Message-ID: <8761r5lk0t.fsf@nautilus.nautilus> (raw)
Hi all,
after an upgrade to latest emacs-snapshot for Debian sid (2:20131201-1)
I got the following warning at emacs start up:
Warning (initialization): Your `load-path' seems to contain
your `.emacs.d' directory: /home/lele/.emacs.d/
This is likely to cause problems...
Consider using a subdirectory instead, e.g.: /home/lele/.emacs.d/lisp
Effectively my own variation of the emacs-starter-kit init.el contains
the following code:
;; Load path etc.
(setq esk-dotfiles-dir (file-name-directory
(or (buffer-file-name) load-file-name))
esk-autoload-file (concat esk-dotfiles-dir "loaddefs.el")
package-user-dir (concat esk-dotfiles-dir "elpa")
esk-custom-file (concat esk-dotfiles-dir "custom")
esk-system-specific-config (concat esk-dotfiles-dir system-name)
esk-user-specific-config (concat esk-dotfiles-dir user-login-name)
esk-user-specific-dir (concat esk-dotfiles-dir user-login-name)
esk-overrides-dir (concat esk-dotfiles-dir "overrides")
custom-file (concat esk-user-specific-config ".el"))
;; Load up ELPA, the package manager
(add-to-list 'load-path esk-dotfiles-dir)
so load-path contains the directory /home/lele/.emacs.d/, that contains
my starter-kit-xxx.el files.
Is that warning telling me that I should move all my starter-kit-xxx.el
files into a lisp/ subdirectory and put the latter in the load-path
list?
OOC, what are the alleged problems that my current configuration could
trigger?
Thanks in advance for any clarification,
bye, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it | -- Fortunato Depero, 1929.
next reply other threads:[~2013-12-03 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 21:08 Lele Gaifax [this message]
2013-12-04 5:17 ` Initialization warning with latest emacs snapshot Jambunathan K
[not found] ` <mailman.8053.1386134281.10748.help-gnu-emacs@gnu.org>
2013-12-04 6:42 ` Damien Wyart
2013-12-04 6:52 ` Jambunathan K
[not found] ` <mailman.8055.1386139943.10748.help-gnu-emacs@gnu.org>
2014-01-28 10:04 ` biot023
2014-01-28 16:03 ` 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=8761r5lk0t.fsf@nautilus.nautilus \
--to=lele@metapensiero.it \
--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).