Re: emacsclient and gnus

Re: emacsclient and gnus

[Richard Riley]

Harry Putnam <reader@newsguy.com> writes:

> I'm new at using emacsclient..  
>
> It hasn't been obvious to me how to gracefully exit emacsclient after
> connecting to a remote emacs running gnus, and I've changed buffer
> into the gnus session from the remote.
>
> To get into the server I said `emacsclient -c' once the emacs frame
> opens I did C-x b *Group* <RET>  and went about my gnus business.
> Now how to leave without shutting gnus down on the server too.
>
> After reading and posting or whatever... if I change buffer back out
> of gnus and attempt to C-x C-s... it still wants to kill the gnus
> session.   Which also kills it on the remote.
>
> C-x # just tells me there are no buffers waiting.
>
> I must have missed it in emacs manual under emacsclient... how to
> close emacs without terminating the gnus session on remote. 
>
>
>

C-x C-c runs the command save-buffers-kill-terminal, which is an
interactive compiled Lisp function in `files.el'.


-- 
 important and urgent problems of the technology of today are no longer the satisfactions of the primary needs or of archetypal wishes, but the reparation of the evils and damages by the technology of yesterday.  ~Dennis Gabor, Innovations:  Scientific, Technological and Social, 1970

Re: emacsclient and gnus

[Harry Putnam]

Richard Riley <rileyrgdev@gmail.com> writes:

>
> C-x C-c runs the command save-buffers-kill-terminal, which is an
> interactive compiled Lisp function in `files.el'.

Well, yes... I do know how to shut emacs down.  But that kills the
gnus session on the server.

Let me describe the whole example:

Start emacs -f gnus on my main desktop (also starts the server).

Later connect to that session from a remote with emacsclient.

emacsclient -c <RET>

C-x b *Group* <RET>  Now I'm in the gnus session.  How do I leave it
without shutting down the server too.  Just switching out of the
buffer and C-x C-c kills the emacsclient terminal alright but it also
kills the gnus session on the server.

Re: emacsclient and gnus

[Tassilo Horn]

Harry Putnam <reader@newsguy.com> writes:

Hi Harry,

> Start emacs -f gnus on my main desktop (also starts the server).
>
> Later connect to that session from a remote with emacsclient.
>
> emacsclient -c <RET>
>
> C-x b *Group* <RET> Now I'm in the gnus session.  How do I leave it
> without shutting down the server too.

`C-x 5 0' should do the trick.

> Just switching out of the buffer and C-x C-c kills the emacsclient
> terminal alright but it also kills the gnus session on the server.

With emacs 23 `C-x C-c' is supposed to do the right thing, e.g. leave
the server running.  Maybe your snapshot is outdated?  For me it just
works...

Bye,
Tassilo
-- 
[Emacs] is written in Lisp, which is the only computer language that is
beautiful.  -- Neal Stephenson, _In the Beginning was the Command Line_

Re: emacsclient and gnus

[Harry Putnam]

Tassilo Horn <tassilo@member.fsf.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
> Hi Harry,
>
>> Start emacs -f gnus on my main desktop (also starts the server).
>>
>> Later connect to that session from a remote with emacsclient.
>>
>> emacsclient -c <RET>
>>
>> C-x b *Group* <RET> Now I'm in the gnus session.  How do I leave it
>> without shutting down the server too.
>
> `C-x 5 0' should do the trick.

Ahh yes it does.

>> Just switching out of the buffer and C-x C-c kills the emacsclient
>> terminal alright but it also kills the gnus session on the server.
>
> With emacs 23 `C-x C-c' is supposed to do the right thing, e.g. leave
> the server running.  Maybe your snapshot is outdated?  For me it just
> works...

I miss spoke earlier in the thread and said closing the emacsclient
session `killed the server too' but I really meant what you quote just
above.. that it kills the gnus session on the server. 

So no, my emacs-23 version is fairly recent, I just wasn't using the right
command to leave the gnus session.
Using the one you suggested C-x 5 0, and C-x C-s does the right thing.

I see that information in the documentation now... I'd seen it before
too but somehow didn't connect it to leaving a gnus session.

If you just change buffers (C-x b) out of gnus then C-x C-s, it does kill gnus
on the server, but that makes sense when I thought about it a little
more.

Thanks

Re: emacsclient and gnus

[Richard Riley]

Harry Putnam <reader@newsguy.com> writes:

> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>> Hi Harry,
>>
>>> Start emacs -f gnus on my main desktop (also starts the server).
>>>
>>> Later connect to that session from a remote with emacsclient.
>>>
>>> emacsclient -c <RET>
>>>
>>> C-x b *Group* <RET> Now I'm in the gnus session.  How do I leave it
>>> without shutting down the server too.
>>
>> `C-x 5 0' should do the trick.
>
> Ahh yes it does.
>
>>> Just switching out of the buffer and C-x C-c kills the emacsclient
>>> terminal alright but it also kills the gnus session on the server.
>>
>> With emacs 23 `C-x C-c' is supposed to do the right thing, e.g. leave
>> the server running.  Maybe your snapshot is outdated?  For me it just
>> works...
>
> I miss spoke earlier in the thread and said closing the emacsclient
> session `killed the server too' but I really meant what you quote just
> above.. that it kills the gnus session on the server. 
>
> So no, my emacs-23 version is fairly recent, I just wasn't using the right
> command to leave the gnus session.
> Using the one you suggested C-x 5 0, and C-x C-s does the right thing.

C-x C-c does not kill the server here. But then I start my emacs in my
.xsession with "emacs --daemon" as documented somewhere for Emacs 23.0.

>
> I see that information in the documentation now... I'd seen it before
> too but somehow didn't connect it to leaving a gnus session.
>
> If you just change buffers (C-x b) out of gnus then C-x C-s, it does kill gnus
> on the server, but that makes sense when I thought about it a little
> more.
>
> Thanks
>
>
>

-- 
 important and urgent problems of the technology of today are no longer the satisfactions of the primary needs or of archetypal wishes, but the reparation of the evils and damages by the technology of yesterday.  ~Dennis Gabor, Innovations:  Scientific, Technological and Social, 1970

Re: emacsclient and gnus

[Tassilo Horn]

Richard Riley <rileyrgdev@gmail.com> writes:

Hi!

>> I miss spoke earlier in the thread and said closing the emacsclient
>> session `killed the server too' but I really meant what you quote
>> just above.. that it kills the gnus session on the server.
>>
>> So no, my emacs-23 version is fairly recent, I just wasn't using the
>> right command to leave the gnus session.  Using the one you suggested
>> C-x 5 0, and C-x C-s does the right thing.
>
> C-x C-c does not kill the server here. But then I start my emacs in my
> .xsession with "emacs --daemon" as documented somewhere for Emacs
> 23.0.

Me, too.  But C-x C-s in any gnus buffer (this message mode buffer,
*Group*, *Summary*, ...) I'm asked to save my drafts, the dribble file
and stuff, so I guess it'll really quit gnus.  Strange...

Bye,
Tassilo
-- 
To be or not to be? That is the question. The answer? Chuck Norris. 

Re: emacsclient and gnus

[Harry P]

Tassilo Horn <tassilo@member.fsf.org> writes:

>> C-x C-c does not kill the server here. But then I start my emacs in my
>> .xsession with "emacs --daemon" as documented somewhere for Emacs
>> 23.0.
>
> Me, too.  But C-x C-s in any gnus buffer (this message mode buffer,
> *Group*, *Summary*, ...) I'm asked to save my drafts, the dribble file
> and stuff, so I guess it'll really quit gnus.  Strange...

I thought so at first but when I thought a little more about it.  It
does make some sense.  

By entering into the gnus session, I've basically taken over that gnus
session, so if I then tell gnus to stop the session (C-x C-s from
emacsclient) it seems that would apply to any session I've taken over.

But with the command you mentioned `C-x 5 0' I've relinquished control
of gnus so then C-x C-s only closes my emacsclient terminal.

Re: emacsclient and gnus

[Harry P]

Tassilo Horn <tassilo@member.fsf.org> writes:

> Me, too.  But C-x C-s in any gnus buffer (this message mode buffer,
> *Group*, *Summary*, ...) I'm asked to save my drafts, the dribble file
> and stuff, so I guess it'll really quit gnus.  Strange...

Whoops, I meant to point out... in my previous message about it making
sense bla bla.

You noticed that it would close gnus when performed from any gnus
buffer, but it will also do that from out side of gnus, like if you
use C-x b to go to some file or the like, and then do C-x C-s in the
client, it will still close gnus on the server.

But again, I think that actually makes sense, because until you've
relinquished control with C-x 5 0 you still own the session.

Re: emacsclient and gnus

[Harry P]

Richard Riley <rileyrgdev@gmail.com> writes:

> C-x C-c does not kill the server here. But then I start my emacs in my
> .xsession with "emacs --daemon" as documented somewhere for Emacs 23.0.

I may have confused things a little on that.. At one point I said it
killed the server but I really meant it killed gnus on the server.  I
actually said both things... sloppy language usage.

Re: emacsclient and gnus

[Richard Riley]

Harry P <reader@newsguy.com> writes:

> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>>> C-x C-c does not kill the server here. But then I start my emacs in my
>>> .xsession with "emacs --daemon" as documented somewhere for Emacs
>>> 23.0.
>>
>> Me, too.  But C-x C-s in any gnus buffer (this message mode buffer,
>> *Group*, *Summary*, ...) I'm asked to save my drafts, the dribble file
>> and stuff, so I guess it'll really quit gnus.  Strange...

C-x C-s has a different meaning in some parts of Gnus. e.g


C-x C-s runs the command gnus-summary-reselect-current-group

>
> I thought so at first but when I thought a little more about it.  It
> does make some sense.  
>
> By entering into the gnus session, I've basically taken over that gnus
> session, so if I then tell gnus to stop the session (C-x C-s from
> emacsclient) it seems that would apply to any session I've taken over.
>
> But with the command you mentioned `C-x 5 0' I've relinquished control
> of gnus so then C-x C-s only closes my emacsclient terminal.

Are you saying C-x C-c does not work for you?

(C-x C-c runs the command save-buffers-kill-terminal)

C-x C-s is simply "save-buffer" in most cases.

-- 
 important and urgent problems of the technology of today are no longer the satisfactions of the primary needs or of archetypal wishes, but the reparation of the evils and damages by the technology of yesterday.  ~Dennis Gabor, Innovations:  Scientific, Technological and Social, 1970

Re: emacsclient and gnus

[Harry Putnam]

Richard Riley <rileyrgdev@gmail.com> writes:

>> By entering into the gnus session, I've basically taken over that gnus
>> session, so if I then tell gnus to stop the session (C-x C-s from
>> emacsclient) it seems that would apply to any session I've ta
C-x C-c runs the command save-buffers-kill-terminal, which is an
interactive compiled Lisp function in `files.el'.ken over.
>>
>> But with the command you mentioned `C-x 5 0' I've relinquished control
>> of gnus so then C-x C-s only closes my emacsclient terminal.
>
> Are you saying C-x C-c does not work for you?
>
> (C-x C-c runs the command save-buffers-kill-terminal)
>
> C-x C-s is simply "save-buffer" in most cases.

Initially I asked how to leave a gnus session when I've entered it in
a running emacs server running gnus.

You offered:
 
> C-x C-c runs the command save-buffers-kill-terminal, which is an
> interactive compiled Lisp function in `files.el'.

I'm saying if I start emacs and then gnus... and then say 
M-x server-start <ret>

Then if I ssh in from a remote... and type emacsclient -c

Then switch into the gnus buffers... If I then say C-x C-s it will
offer to close gnus.  Not what I want... I want to close the
emacsclient terminal without closing gnus.

If I say C-x 5-0 then that is what happens.

Re: emacsclient and gnus

[Tassilo Horn]

Harry Putnam <reader@newsguy.com> writes:

Hi Harry,

>> C-x C-c runs the command save-buffers-kill-terminal, which is an
>> interactive compiled Lisp function in `files.el'.
>
> I'm saying if I start emacs and then gnus... and then say M-x
> server-start <ret>
>
> Then if I ssh in from a remote... and type emacsclient -c
>
> Then switch into the gnus buffers... If I then say C-x C-s it will
> offer to close gnus.  Not what I want... I want to close the
> emacsclient terminal without closing gnus.

I think most of the confusion in this thread is that you always write
`C-x C-s' and not `C-x C-c'.  Is that really what you type?  Or did you
rebind `C-x C-s' to do something different from `save-buffer'?

If I got you correctly you say that `C-x C-c' closes gnus, but lets the
emacs server alive, so you can reconnect with emacsclient and then gnus
is really closed.  If that's true, I think it's really strange, and I'd
suggest that you describe that on the gnus mailing list (ding@gnus.org).
IMHO `C-x C-c' shouldn't behave different when inside gnus buffers than
inside any other buffer.

> If I say C-x 5-0 then that is what happens.

That's save in every situation. ;-)

Bye,
Tassilo

Re: emacsclient and gnus

[Richard Riley]

Harry Putnam <reader@newsguy.com> writes:

> Richard Riley <rileyrgdev@gmail.com> writes:
>
>>> By entering into the gnus session, I've basically taken over that gnus
>>> session, so if I then tell gnus to stop the session (C-x C-s from
>>> emacsclient) it seems that would apply to any session I've ta
> C-x C-c runs the command save-buffers-kill-terminal, which is an
> interactive compiled Lisp function in `files.el'.ken over.
>>>
>>> But with the command you mentioned `C-x 5 0' I've relinquished control
>>> of gnus so then C-x C-s only closes my emacsclient terminal.
>>
>> Are you saying C-x C-c does not work for you?
>>
>> (C-x C-c runs the command save-buffers-kill-terminal)
>>
>> C-x C-s is simply "save-buffer" in most cases.
>
> Initially I asked how to leave a gnus session when I've entered it in
> a running emacs server running gnus.
>
> You offered:
>  
>> C-x C-c runs the command save-buffers-kill-terminal, which is an
>> interactive compiled Lisp function in `files.el'.
>
> I'm saying if I start emacs and then gnus... and then say 
> M-x server-start <ret>
>
> Then if I ssh in from a remote... and type emacsclient -c
>
> Then switch into the gnus buffers... If I then say C-x C-s it will
> offer to close gnus.  Not what I want... I want to close the
> emacsclient terminal without closing gnus.

I am really confused Harry to be honest. I keep listing the command name
along with the keyboard binding (always a good idea IMO) but you keep
going back to C-x C-s - whereas I am saying C-x C-c (C-x C-c runs the
command save-buffers-kill-terminal) does what you want in my setup which
is also emacsclient.

>
> If I say C-x 5-0 then that is what happens.
>

Yes, delete-frame.

But you have a solution so thats the main thing.


-- 
 important and urgent problems of the technology of today are no longer the satisfactions of the primary needs or of archetypal wishes, but the reparation of the evils and damages by the technology of yesterday.  ~Dennis Gabor, Innovations:  Scientific, Technological and Social, 1970

Re: emacsclient and gnus

[reader]

Richard Riley <rileyrgdev@gmail.com> writes:

> I am really confused Harry to be honest. I keep listing the command name
> along with the keyboard binding (always a good idea IMO) but you keep
> going back to C-x C-s - whereas I am saying C-x C-c (C-x C-c runs the
> command save-buffers-kill-terminal) does what you want in my setup which
> is also emacsclient.
>
>>
>> If I say C-x 5-0 then that is what happens.
>>
>
> Yes, delete-frame.
>
> But you have a solution so thats the main thing.

I think this thread is done... I'm terribly terribly sorry for
injecting this amount of confusion.

I've misread your command (C-x C-c) at least 500 times now and continued
to prattle on.  A small amount of knowledge... enough to get on line
is a dangerous thing in my hands... it seems.

I really only meant to say thanks to T. Horne for reminding me of
C-x 5 0  and I finally see I needed to thank you as well for C-x C-c
which does exactly what you've mentioned.

So to finally leave you both alone and hide my head for a while.

Thank you both for an incredible amount of patience.  

I'm not old enough to be this senile... if I'm this bad at 62, I'll
need a restraining order to keep me off the internet by 65.

Once more... I'm very sorry to have wasted both your time.  You both
have shown and incredible amount of patience... real testimony to the
lack of any animosity, or other need to flame and snipe here in this
group. 

emacsclient and gnus

[Harry Putnam]

I'm new at using emacsclient..  

It hasn't been obvious to me how to gracefully exit emacsclient after
connecting to a remote emacs running gnus, and I've changed buffer
into the gnus session from the remote.

To get into the server I said `emacsclient -c' once the emacs frame
opens I did C-x b *Group* <RET>  and went about my gnus business.
Now how to leave without shutting gnus down on the server too.

After reading and posting or whatever... if I change buffer back out
of gnus and attempt to C-x C-s... it still wants to kill the gnus
session.   Which also kills it on the remote.

C-x # just tells me there are no buffers waiting.

I must have missed it in emacs manual under emacsclient... how to
close emacs without terminating the gnus session on remote.