[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: address@hidden: emacsclient won't open new frame on remote display]
From: |
Stefan Monnier |
Subject: |
Re: address@hidden: emacsclient won't open new frame on remote display] |
Date: |
Fri, 07 Jul 2006 11:21:21 -0400 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
>>> 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.
Thanks. I haven't had the time to test it yet, but it looks good.
Stefan