From: William Gardella <gardellawg@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 7629@debbugs.gnu.org
Subject: bug#7629: 23.2; Remote X Emacsclient Frame Issue
Date: Tue, 21 Dec 2010 14:57:38 -0500 [thread overview]
Message-ID: <87r5daoq4t.fsf@lw-wireless-pittnet-40-144.wireless.pitt.edu> (raw)
In-Reply-To: <87k4j3tupl.fsf@stupidchicken.com>
On Tue, 21 Dec 2010 16:07:34 +0800, Chong Yidong <cyd@stupidchicken.com> wrote:
> William Gardella <gardellawg@gmail.com> writes:
>
> > 6. If I have already closed my remote X emacsclient, the first server
> > appears completely unresponsive and cannot be revived with, e.g.,
> > emacsclient --eval \(server-start\). All subsequent attempts to
> > connect an emacsclient go to the new server process.
>
> I believe this is a known problem with GTK builds of Emacs. GTK cannot
> handle disconnections gracefully; see etc/PROBLEMS. In the current
> pretest (which will be 23.3), Emacs will handle this by aborting if the
> X connection closes.
Thank you for your reply--I have an additional piece of information,
discovered through trial and error.
If started locally with my emacsclient -c --alternate-editor="" script,
the Emacs server creates its socket at /tmp/emacs1000/server
If started remotely with the same script, but executed from my netbook
via ssh -X, the Emacs server creates its socket at
/tmp/user/1000/emacs1000/server.
I don't know if this is related to the issue or not, but it does prevent
"emacsclient -c" from finding itself on the host machine unless I
specify --socket-name.
Best,
--
William Gardella
J.D. Candidate
Class of 2011, University of Pittsburgh School of Law
next prev parent reply other threads:[~2010-12-21 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 5:33 bug#7629: 23.2; Remote X Emacsclient Frame Issue William Gardella
2010-12-21 8:07 ` Chong Yidong
2010-12-21 19:57 ` William Gardella [this message]
2010-12-22 22:35 ` Stefan Monnier
2010-12-23 1:58 ` William Gardella
2010-12-29 4:00 ` Chong Yidong
2014-02-03 23:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5daoq4t.fsf@lw-wireless-pittnet-40-144.wireless.pitt.edu \
--to=gardellawg@gmail.com \
--cc=7629@debbugs.gnu.org \
--cc=cyd@stupidchicken.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 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.