From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Richard Kim <emacs18@gmail.com>, 25163@debbugs.gnu.org
Subject: bug#25163: 26.0.50; Unable to access `user-emacs-directory' (~/.emacs.d/)
Date: Sun, 11 Dec 2016 17:15:39 -0500 [thread overview]
Message-ID: <CAM-tV--zDnm9joSMoG_D=B-Lko1mEtjAhA8Z1G4dZ4g2ohjujA@mail.gmail.com> (raw)
In-Reply-To: <83h96ae5ia.fsf@gnu.org>
On Sun, Dec 11, 2016 at 12:32 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Noam Postavsky <npostavs@users.sourceforge.net>
>> Date: Sun, 11 Dec 2016 10:50:49 -0500
>> Cc: Richard Kim <emacs18@gmail.com>, 25163@debbugs.gnu.org
>>
>> >> Perhaps the warning could be delayed until after init time?
>> >
>> > What would that do to the value of abbrev-file-name?
>>
>> Nothing, only the warning should be delayed.
>
> But Emacs will then create .emacs.d, something the OP didn't want,
> right?
The OP already created an unwritable .emacs.d, so I think that's not
the problem. It's only the non-suppressable warning. Unless I've
misread?
next prev parent reply other threads:[~2016-12-11 22:15 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 [this message]
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='CAM-tV--zDnm9joSMoG_D=B-Lko1mEtjAhA8Z1G4dZ4g2ohjujA@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--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).