GNU bug report logs -
#43645
26.3; emacsclient -c does not open to correct window
Previous Next
Reported by: Blue track <bluetrack121 <at> gmail.com>
Date: Sun, 27 Sep 2020 09:43:02 UTC
Severity: normal
Tags: fixed
Found in version 26.3
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #44 received at 43645 <at> debbugs.gnu.org (full text, mbox):
> Cc: bluetrack121 <at> gmail.com, 43645 <at> debbugs.gnu.org
> From: martin rudalics <rudalics <at> gmx.at>
> Date: Mon, 28 Sep 2020 17:02:13 +0200
>
> >> diff --git a/lisp/server.el b/lisp/server.el
> >> index 436a6ca0c7..f24f8d2b7c 100644
> >> --- a/lisp/server.el
> >> +++ b/lisp/server.el
> >> @@ -1602,7 +1602,7 @@ server-switch-buffer
> >> ;; OK, we know next-buffer is live, let's display and select it.
> >> (if (functionp server-window)
> >> (funcall server-window next-buffer)
> >> - (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.
Lars, can you try Martin's proposal and see if it solves the problem
without any adverse side effects on other use cases?
Thanks.
This bug report was last modified 4 years and 237 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.