[multi-tty] emacsclient and buffers

[multi-tty] emacsclient and buffers

[csant]

Karoly Lorentey said in a message:

       Frames are associated with the emacsclient session they were
       created in.  C-x 5 2 makes the new frame inherit the association
       as well.  When the user closes the last frame associated with a
       particular emacsclient session, emacsclient exits automatically,
       and vice versa.  C-x C-c is rebound to exit the client, not Emacs
       itself.

But how do buffers behave with respect to these frames?

If I have the client open a file from command line
	$ emacsclient file1
and then find another file, C-x C-f file2 in the same frame, is there one,  
or are there two buffers "associated with the emacsclient session"?  If I  
C-x C-c in the client, it will exit, but leave file2 in the buffer list of  
the emacs server instance.

It seems as if only the file opened from command line is associated with  
the client frame: no matter whether file1 or file2 are in the foreground  
in the client frame, if I C-x C-c in the client, file2 will stay in the  
buffer list of the server.  (Amusing side note: to my bewilderment, this  
happened when I C-x C-f a file with tramp as root from within the client,  
and later found that very file still open in the server's buffer list).  I  
can also kill file1 from within the server, and this will terminate the  
client, allthough file2 is still open in the bufferlist.

If this is expected behaviour, I guess it might need some good user  
documentation.

Also, in terminal (-nw and -t respectively) it is not possible to switch  
to a buffer which is currently in the foreground in another frame (emacs  
server, or client).

Kind regards,
/c

Re: [multi-tty] emacsclient and buffers

[David Kastrup]

csant <csant@csant.info> writes:

> It seems as if only the file opened from command line is associated
> with the client frame: no matter whether file1 or file2 are in the
> foreground in the client frame, if I C-x C-c in the client, file2
> will stay in the buffer list of the server.  (Amusing side note: to
> my bewilderment, this happened when I C-x C-f a file with tramp as
> root from within the client, and later found that very file still
> open in the server's buffer list).  I can also kill file1 from
> within the server, and this will terminate the client, allthough
> file2 is still open in the bufferlist.
>
> If this is expected behaviour, I guess it might need some good user
> documentation.
>
> Also, in terminal (-nw and -t respectively) it is not possible to
> switch to a buffer which is currently in the foreground in another
> frame (emacs server, or client).

While I agree with your points, those are usability issues that are
annoying, not critical.

I suppose that once we merge multi-tty, lots of people will start
removing their favorite annoyances.

In this particular case, one would probable not consider the frames
open from one "terminal" when considering how to arrange the frames in
another.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum