From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: [ottomaddox@fastmail.fm: emacsclient won't open new frame on remote display]
Date: Thu, 06 Jul 2006 18:49:41 -0400 [thread overview]
Message-ID: <87ejwy1h8a.fsf@stupidchicken.com> (raw)
In-Reply-To: <jwvac7m9ydv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 06 Jul 2006 18:14:07 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> This suggested change causes Emacs to create a new frame displaying some
>>> random buffer. If server.el subsequently uses switch-to-buffer or something
>>> like that, it's probably OK, but if it instead uses something like
>>> pop-to-buffer because you want to display emacsclient buffers in their own
>>> window or frame, then you end up with 2 windows (or frames) one of which
>>> displays some random buffer.
>
>> As the original bug report indicates, the current default behavior is
>> that the buffer is not displayed at all, which is clearly broken. My
>> thinking is that it makes more sense to create the new frame, to
>> ensure that the default behavior (with no customizations) works. If
>> the user customizes the emacsserver behavior, like changing it to use
>> pop-to-buffer, those personal customizations can be adapted to work
>> with extra displays. But the default behavior must definitely work.
>
>> What do you think?
>
> The OP's problem is indeed clearly a bug. I was just pointing out why your
> patch is not a good fix.
I've checked in a fix that I think addresses your objection.
next prev parent reply other threads:[~2006-07-06 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 17:25 [ottomaddox@fastmail.fm: emacsclient won't open new frame on remote display] Richard Stallman
2006-07-04 20:16 ` Chong Yidong
2006-07-04 21:04 ` Stefan Monnier
2006-07-05 13:17 ` Chong Yidong
2006-07-06 22:14 ` Stefan Monnier
2006-07-06 22:49 ` Chong Yidong [this message]
2006-07-07 15:21 ` Stefan Monnier
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=87ejwy1h8a.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--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).