From: Stephen Berman <Stephen.Berman@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: multi-tty problems involving virtual terminal
Date: Fri, 23 Nov 2007 15:31:45 +0100 [thread overview]
Message-ID: <87r6ihowxa.fsf@escher.local.home> (raw)
In-Reply-To: 200709200117.l8K1HuA0010006@oogie-boogie.ics.uci.edu
Sorry for the long delayed response.
On Wed, 19 Sep 2007 18:17:56 -0700 Dan Nicolaescu <dann@ics.uci.edu> wrote:
> Stephen Berman <Stephen.Berman@gmx.net> writes:
>
> > GNU Emacs 23.0.50.3 (i686-pc-linux-gnu, GTK+ Version 2.10.6) of
> > 2007-09-17 on escher
> >
> > I recently updated to the post-multi-tty merge and have only begun to
> > experiment with it. The first couple of uses, involving the Linux
> > console X client, were unproblematic, but today I unexpectedly had to
> > use the multi-tty functionality from a virtual terminal and ran into
> > some problems. Before updating I didn't follow the various multi-tty
> > threads very closely, so if what I describe below has come up before,
> > I would appreciate a pointer and apologize for the redundancy.
> >
> > I had Emacs running under X with the Emacs server started, as usual.
> > Suddenly X locked up, but I was able to switch to a virtual terminal
> > and invoked emacsclient, and everything was fine, all the buffers of
> > my Emacs started under X were still open. Then I killed the X server
> > and restarted it. When I logged in to the KDE desktop again, I
> > noticed that Emacs (still only running as a client on the virtual
> > terminal) was consuming 99% CPU. I tried to exit Emacs on the virtual
> > terminal with C-x C-c but it failed with a message to the effect
> > "Cannot iconify sole frame" (I don't remember the exact wording). I
> > went back to the KDE desktop and invoked emacsclient again, starting
> > an X client. Then I returned to the virtual terminal and tried C-x
> > C-c again; this time I got the message "The server still has clients;
> > delete them? (yes or no)." I type no and hit return and the virtual
> > terminal immediately locked up without making a line feed. I went
> > back to X and the Emacs X client was gone and in the shell from which
> > I had invoked it was the message "Waiting for Emacs...". The
> > emacsclient process launched from the virtual terminal was still
> > running; I killed it but still the terminal remains locked up and I do
> > not know how to unlock it.
>
> A bug fixing problems with Gtk+ and closing the X11 connection was
> checked in yesterday. Could you please try again your scenario?
In the intervening time I haven't had a spontaneous lockup of X so I
could not exactly reproduce the scenario. (I did have occasion to start
emacsclient from a virtual console after X locked up, but that involved
an Emacs bug in the Gtk+ tool bar (since fixed) and I had to kill the
emacs process to unlock X.) But I just tried the following on GNU Emacs
23.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.12.0) of 2007-11-21 on
escher. I switched from X with a running Emacs to a virtual console,
there invoked emacsclient -t and got my running Emacs session. I typed
C-z and in the shell restarted the X server. Before logging back on to
KDE I returned to the virtual console and typed fg, and the shell
returned the string "emacsclient -t" but in fact no emacs or emacsclient
process was running any more. Is this the expected behavior? (In other
words, killing X under which Emacs is running also kills Emacs clients
spawned in a virtual console?)
Steve Berman
prev parent reply other threads:[~2007-11-23 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 21:31 multi-tty problems involving virtual terminal Stephen Berman
2007-09-20 1:17 ` Dan Nicolaescu
2007-11-23 14:31 ` Stephen Berman [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=87r6ihowxa.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@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.