bug#43645: 26.3; emacsclient -c does not open to correct window

[Lars Ingebrigtsen]

martin rudalics <rudalics@gmx.at> writes:

>>> -   (let ((win (get-buffer-window next-buffer 0)))
>>> +   (let ((win (get-buffer-window next-buffer)))
>>>       (if (and win (not server-window))
>>>           ;; The buffer is already displayed: just reuse the
>>>           ;; window.  If FILEPOS is non-nil, use it to replace the
>>>
>>
>> Martin, any comments on this?
>
> Wouldn't the "0" make sense when invoking emacsclient without an option
> like -c or -t?  IIUC, in that case we should try to reuse some existing
> visible or iconified window.  But ... I never use emacsclient.

Hm, yes...   The behavioural change would be if you already have two
frames open, with the buffer showing in a window on frame A, but frame B
currently has focus, then "emacsclient test.txt" would pop up that
buffer in frame B, too.

So the 0 should be there in the "emacsclient test.txt" case, but not in
the "emacsclient -c test.txt" (and -t) cases.  I'll see if I can come up
with a fix...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no