all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: Glenn Morris <rgm@gnu.org>
Cc: reinhard.kotucha@web.de, 16154@debbugs.gnu.org
Subject: bug#16154: Emacs crashes if $HOME isn't writable
Date: Mon, 16 Dec 2013 08:24:42 +0100	[thread overview]
Message-ID: <87wqj5xnph.fsf@Rainer.invalid> (raw)
In-Reply-To: <7yob4hrj4t.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 15 Dec 2013 14:47:46 -0500")

Glenn Morris writes:
> Not sure why you guys are saying this works in 24.3, because I only
> fixed this in trunk semi-recently:
>
> http://debbugs.gnu.org/13930
>
> Ie, this should be fixed in 24.4.

It "worked for me" since I didn't test with enough command line
arguments to see that the processing of the command line would be
incomplete in 24.3.

> Of course, "refuses to do anything useful" is very vague, so I have no
> way to test whatever the OP was seeing works now.

It's become clear in the meantime that the bug is indeed that file(s)
given on the command line won't open in 24.3.  You can still work on
them once Emacs has started and complained about the non-writable
~/.emacs.d/, though.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables





      parent reply	other threads:[~2013-12-16  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-15  7:59 bug#16154: Emacs crashes if $HOME isn't writable Reinhard Kotucha
2013-12-15 11:40 ` Achim Gratz
2013-12-15 16:25   ` Eli Zaretskii
2013-12-15 19:47     ` Glenn Morris
2013-12-15 20:17       ` Eli Zaretskii
2013-12-16  3:01       ` Reinhard Kotucha
2013-12-16 21:15         ` Reinhard Kotucha
2013-12-16  7:24       ` Achim Gratz [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wqj5xnph.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=16154@debbugs.gnu.org \
    --cc=reinhard.kotucha@web.de \
    --cc=rgm@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.