unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lluís <xscript@gmx.net>
To: Dan Nicolaescu <dann@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Finishing ssh session with "emacsclient -t" kills emacs daemon
Date: Thu, 15 Aug 2013 12:49:33 +0300	[thread overview]
Message-ID: <874nar9tci.fsf@fimbulvetr.bsc.es> (raw)
In-Reply-To: <yxqob904agw.fsf@fencepost.gnu.org> (Dan Nicolaescu's message of "Wed, 14 Aug 2013 10:23:59 -0400")

Dan Nicolaescu writes:

> Lluís <xscript@gmx.net> writes:
>> I'd like to keep a daemon running on a server:
>> 
>> ssh server "nohup emacs --daemon"

> Is this emacs compiled with the Gtk+ toolkit? 

Yes it is.


>> Then, be able to connect to it from different machines using the graphical
>> frontend:
>> 
>> ssh -X server "nohup emacsclient -c"
>> 
>> The problem is that the ssh gets "stuck" after exiting emacs, and whenever I C-c
>> it, the daemon just dies. The same happens if I do this "manually":
>> 
>> ssh -X server
>> emacsclient -c
>> exit
>> 
>> The ssh client gets stuck on the exit, and using C-c finishes the ssh session
>> together with the emacs daemon. If instead I use the terminal frontend,
>> everything works fine:
>> 
>> ssh -X server
>> emacsclient -t
>> exit
>> 
>> but that's not what I want.
>> 
>> As a side note, using this:
>> 
>> ssh server "nohup emacsclient -c"
>> 
>> results in the error "emacsclient: could not get terminal name".
>> 
>> 
>> Is there any way around the first problem?

-- 
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth



  reply	other threads:[~2013-08-15  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 12:44 Finishing ssh session with "emacsclient -t" kills emacs daemon Lluís
2013-08-14 14:23 ` Dan Nicolaescu
2013-08-15  9:49   ` Lluís [this message]
2013-08-15 10:01     ` Lluís
2013-08-15 11:25       ` Óscar Fuentes
2013-08-15 12:30         ` Lluís
2013-08-15 20:48       ` Dan Nicolaescu

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=874nar9tci.fsf@fimbulvetr.bsc.es \
    --to=xscript@gmx.net \
    --cc=dann@gnu.org \
    --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 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).