From: npostavs@users.sourceforge.net
To: Richard Kim <emacs18@gmail.com>
Cc: 25163@debbugs.gnu.org
Subject: bug#25163: 26.0.50; Unable to access `user-emacs-directory' (~/.emacs.d/)
Date: Sat, 10 Dec 2016 23:24:06 -0500 [thread overview]
Message-ID: <8760mrdrfd.fsf@users.sourceforge.net> (raw)
In-Reply-To: <qtma8c3qgua.fsf@gmail.com> (Richard Kim's message of "Sat, 10 Dec 2016 19:34:21 -0800")
Richard Kim <emacs18@gmail.com> writes:
> My build of emacs 26 (git repo version 25a52ca of 2016/12/10)
> starts up with the following warning:
>
> Warning (initialization): Unable to access `user-emacs-directory' (~/.emacs.d/).
> Any data that would normally be written there may be lost!
> If you never want to see this message again,
> customize the variable `user-emacs-directory-warning'.
>
> This is despite setting the variable as suggested to suppress such warning.
> I think this warning should not be printed.
>
> Emacs is started like this:
>
> chmod 0 ~/.emacs.d
> ~/opt/emacs26/bin/emacs -q \
> --eval '(setq user-emacs-directory (expand-file-name "~/elisp/"))' \
> --eval '(setq user-emacs-directory-warning nil)'
>
> Emacs 25 (git repo build of emacs-25 branch) started the same way does
> not print this warning.
I see the same in Emacs 25, 24.5, and 24.4; 24.3 just prints a "File
exists" message. Looks like the problem is that locate-user-emacs-file
(and thus the check for the warning) is called before any customizations
(or --eval args) are executed. Here's a backtrace I got by putting
(debug) inside locate-user-emacs-file, just before the `display-warning'
call:
Debugger entered: nil
locate-user-emacs-file("abbrev_defs" ".abbrev_defs")
#[0 "\300\301\302\"\207" [locate-user-emacs-file "abbrev_defs" ".abbrev_defs"] 3]()
funcall(#[0 "\300\301\302\"\207" [locate-user-emacs-file "abbrev_defs" ".abbrev_defs"] 3])
eval((funcall (function #[0 "\300\301\302\"\207" [locate-user-emacs-file "abbrev_defs" ".abbrev_defs"] 3])))
custom-reevaluate-setting(abbrev-file-name)
mapc(custom-reevaluate-setting (temporary-file-directory transient-mark-mode small-temporary-file-directory auto-save-file-name-transforms remote-shell-program Info-default-directory-list rmail-spool-directory abbrev-file-name auto-encryption-mode blink-cursor-mode tutorial-directory global-font-lock-mode file-name-shadow-mode query-replace-from-to-separator image-load-path mouse-wheel-mode electric-indent-mode electric-quote-mode global-eldoc-mode tooltip-mode))
command-line()
normal-top-level()
Perhaps the warning could be delayed until after init time?
next prev parent reply other threads:[~2016-12-11 4:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 3:34 bug#25163: 26.0.50; Unable to access `user-emacs-directory' (~/.emacs.d/) Richard Kim
2016-12-11 4:24 ` npostavs [this message]
2016-12-11 8:38 ` Tino Calancha
2016-12-11 14:07 ` npostavs
2016-12-12 2:41 ` Tino Calancha
2022-04-21 15:28 ` Lars Ingebrigtsen
2016-12-11 15:28 ` Eli Zaretskii
2016-12-11 15:50 ` Noam Postavsky
2016-12-11 17:32 ` Eli Zaretskii
2016-12-11 22:15 ` Noam Postavsky
2016-12-11 22:26 ` Óscar Fuentes
2016-12-12 3:28 ` Eli Zaretskii
2016-12-12 4:07 ` Óscar Fuentes
2016-12-13 2:19 ` Richard Kim
2016-12-13 15:52 ` Eli Zaretskii
2016-12-13 2:40 ` Glenn Morris
2016-12-13 4:02 ` Óscar Fuentes
2018-06-13 1:24 ` Noam Postavsky
2020-08-24 15:54 ` Lars Ingebrigtsen
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=8760mrdrfd.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25163@debbugs.gnu.org \
--cc=emacs18@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).