unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Prije <rprije@janestreet.com>, 13930@debbugs.gnu.org
Subject: bug#13930: Emacs doesn't cope well if it can't access/create .emacs.d
Date: Tue, 12 Mar 2013 12:29:23 -0400	[thread overview]
Message-ID: <yfmwu8a8f0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83vc8wk39s.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 12 Mar 2013 18:10:23 +0200")

Eli Zaretskii wrote:

>> It does exactly the same thing with --debug-init (says "creating directory:
>> permission denied...") and supplies no further information.
>
> How about running it under GDB with a breakpoint on report_file_error
> and on xsignal?  If you start GDB from the src directory of the Emacs
> sources, the .gdbinit file there defines a command xbacktrace which
> will produce a Lisp-level backtrace in addition to the C-level
> backtrace produced by the "bt" command of GDB.

Why do we need to jump through such hoops, when locate-user-emacs-file,
which Stefan has just added all over the place, says:

  Else return NEW-NAME in `user-emacs-directory', creating the
  directory if it does not exist.





  reply	other threads:[~2013-03-12 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  1:35 bug#13930: Emacs doesn't cope well if it can't access/create .emacs.d Robert Prije
2013-03-12  3:43 ` Stefan Monnier
2013-03-12  3:52   ` Robert Prije
2013-03-12  5:11     ` Stefan Monnier
2013-03-12  9:01       ` Robert Prije
2013-03-12 16:10     ` Eli Zaretskii
2013-03-12 16:29       ` Glenn Morris [this message]
2013-03-12 16:48         ` Eli Zaretskii
2013-03-12 16:32       ` Sven Joachim
2013-05-12 23:33         ` Robert Prije
2013-05-14  7:30           ` Glenn Morris
2013-05-14  8:46             ` Robert Prije
2013-05-14 16:01               ` Glenn Morris

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=yfmwu8a8f0.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=13930@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rprije@janestreet.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).