From: David Kastrup <dak@gnu.org>
To: csant <csant@csant.info>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [multi-tty] emacsclient and buffers
Date: Thu, 24 May 2007 22:36:30 +0200 [thread overview]
Message-ID: <85odka3qnl.fsf@lola.goethe.zz> (raw)
In-Reply-To: <op.tsufnzokd84skq@fiore.malebolge> (csant@csant.info's message of "Thu\, 24 May 2007 20\:15\:25 +0200")
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
prev parent reply other threads:[~2007-05-24 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 18:15 [multi-tty] emacsclient and buffers csant
2007-05-24 20:36 ` David Kastrup [this message]
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=85odka3qnl.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=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).