From: csant <csant@csant.info>
To: emacs-devel <emacs-devel@gnu.org>
Subject: [multi-tty] emacsclient and buffers
Date: Thu, 24 May 2007 20:15:25 +0200 [thread overview]
Message-ID: <op.tsufnzokd84skq@fiore.malebolge> (raw)
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
next reply other threads:[~2007-05-24 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 18:15 csant [this message]
2007-05-24 20:36 ` [multi-tty] emacsclient and buffers David Kastrup
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=op.tsufnzokd84skq@fiore.malebolge \
--to=csant@csant.info \
--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).