all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36902@debbugs.gnu.org, leo <devel@halloleo.hailmail.net>
Subject: bug#36902: Emacs crashed under X11 suddenly
Date: Wed, 21 Aug 2019 17:42:31 +0200	[thread overview]
Message-ID: <CADwFkmmwRJrNqxcvf4LVbwrNb_1EUtc4qi8BtdSe-P3ACVcQcQ@mail.gmail.com> (raw)
In-Reply-To: <B7312636-64D2-4D0A-AA1A-5F78FE588B38@halloleo.hailmail.net>

tags 36902 + notabug
close 36902
quit

Eli Zaretskii <eliz@gnu.org> writes:

>> From: leo <devel@halloleo.hailmail.net>
>> Cc: 36902@debbugs.gnu.org
>> Date: Sun, 11 Aug 2019 19:35:23 +1000
>>
>> Yes, I have sometimes trouble interrupted X sessions.
>>
>> Sorry to hog you her on the bugs email, but is there a way to keep emacs
>> alive when the X session disappears? And then later, is it possible to
>> reconnect to that emacs session via a DISPLAY?
>
> You could start Emacs as a daemon and close the frames when you make a
> break, then X problems should not cause any harm, and you can restore
> the frames later with emacsclient.
>
> Otherwise, I don't think we can survive X problems which happen while
> you actually type.

So this does not seem to be due to Emacs, but due to interrupted X
sessions.  The workaround is to start Emacs as a daemon and use
emacsclient.

I'm therefore closing this as notabug.  Please reopen if there is
something that I've misunderstood.

Thanks,
Stefan Kangas





      parent reply	other threads:[~2019-08-21 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03  6:34 bug#36902: Emacs crashed under X11 suddenly leo
2019-08-03  7:03 ` Eli Zaretskii
2019-08-07 23:30   ` leo
2019-08-10  9:00     ` Eli Zaretskii
2019-08-11  9:35       ` leo
2019-08-11 14:18         ` Eli Zaretskii
2019-08-21 15:42 ` Stefan Kangas [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=CADwFkmmwRJrNqxcvf4LVbwrNb_1EUtc4qi8BtdSe-P3ACVcQcQ@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=36902@debbugs.gnu.org \
    --cc=devel@halloleo.hailmail.net \
    --cc=eliz@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.