unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>, 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: Mon, 12 Dec 2016 05:07:54 +0100	[thread overview]
Message-ID: <8760mpx011.fsf@wanadoo.es> (raw)
In-Reply-To: <83r35dddvv.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Dec 2016 05:28:52 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> The underlying problem is that Emacs uses user-emacs-directory and
>> user-emacs-directory-warning before any user-customization is made
>> effective.
>> 
>> Emacs not being aware of the user setting user-emacs-directory-warning
>> is annoying and can be solved by delaying the warning, but the part
>> about user-emacs-directory looks more concerning.
>
> Yes, those are my concerns exactly.
>
> More generally, Emacs supports only one method of pointing that
> directory to another place, and that is via the -u command-line
> option.  We could perhaps support other methods as well, like the one
> the OP uses, but IMO it will require more changes than just delaying
> the warning.

I guess that the OP is exceptional among the Emacs user base when he
resorts to --eval '(setq user-emacs-directory ...)' because he is not
aware of the correct and simple -u command line option. If that's the
case, his problem should be completely solved by using -u (without need
to set user-emacs-directory-warning).

I propose to change the docstring of user-emacs-directory to mention -u
as the correct method and recommend against setting that variable in any
way. Sadly, we cannot remove it altogether.

As for user-emacs-directory-warning, leave it alone. Actually, in this
case it was doing its job.





  reply	other threads:[~2016-12-12  4:07 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
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 [this message]
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=8760mpx011.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --cc=25163@debbugs.gnu.org \
    --cc=eliz@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).