Finishing ssh session with "emacsclient -t" kills emacs daemon

Finishing ssh session with "emacsclient -t" kills emacs daemon

[Lluís]

I'd like to keep a daemon running on a server:

    ssh server "nohup emacs --daemon"

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?


Thanks,
  Lluis

-- 
 "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

Re: Finishing ssh session with "emacsclient -t" kills emacs daemon

[Dan Nicolaescu]

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? 


> 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?
>
>
> Thanks,
>   Lluis
>
> -- 
>  "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

Re: Finishing ssh session with "emacsclient -t" kills emacs daemon

[Lluís]

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

Re: Finishing ssh session with "emacsclient -t" kills emacs daemon

[Lluís]

Lluís  writes:

> 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.

I just realized that the emacs-lucid package does not have this problem. Is this
supposed to behave like this?


Thanks,
  Lluis

Re: Finishing ssh session with "emacsclient -t" kills emacs daemon

[Óscar Fuentes]

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.
>
> I just realized that the emacs-lucid package does not have this
> problem. Is this supposed to behave like this?

The problem you experienced with Emacs/Gtk+ is a long-standing one.

This is an old PR from yours truly:

http://debbugs.gnu.org/db/33/3360.html

Re: Finishing ssh session with "emacsclient -t" kills emacs daemon

[Lluís]

Óscar Fuentes 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.
>> 
>> I just realized that the emacs-lucid package does not have this
>> problem. Is this supposed to behave like this?

> The problem you experienced with Emacs/Gtk+ is a long-standing one.

> This is an old PR from yours truly:

> http://debbugs.gnu.org/db/33/3360.html

Well, looks like I'll have to stick with lucid for some more time when doing
remote connections :)

Thanks for the info

-- 
 "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

Re: Finishing ssh session with "emacsclient -t" kills emacs daemon

[Dan Nicolaescu]

Lluís <xscript@gmx.net> writes:

> Lluís  writes:
>
>> 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.
>
> I just realized that the emacs-lucid package does not have this problem. Is this
> supposed to behave like this?

emacs --daemon 

should print a warning about the Gtk+ version having a problem.  
The problem is a long standing Gtk+ bug.