From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: bluetrack121@gmail.com, larsi@gnus.org, 43645@debbugs.gnu.org
Subject: bug#43645: 26.3; emacsclient -c does not open to correct window
Date: Tue, 29 Sep 2020 17:06:48 +0300 [thread overview]
Message-ID: <83a6x8lls7.fsf@gnu.org> (raw)
In-Reply-To: <b8839d63-4f7e-8f63-95b8-cf9c3560f3a9@gmx.at> (message from martin rudalics on Mon, 28 Sep 2020 17:02:13 +0200)
> Cc: bluetrack121@gmail.com, 43645@debbugs.gnu.org
> From: martin rudalics <rudalics@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.
next prev parent reply other threads:[~2020-09-29 14:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 6:41 bug#43645: 26.3; emacsclient -c does not open to correct window Blue track
2020-09-27 9:58 ` Eli Zaretskii
2020-09-27 10:36 ` Blue track
2020-09-27 10:54 ` Eli Zaretskii
2020-09-27 16:02 ` Lars Ingebrigtsen
2020-09-27 16:09 ` Eli Zaretskii
2020-09-27 16:21 ` Lars Ingebrigtsen
2020-09-27 16:33 ` Eli Zaretskii
2020-09-27 16:44 ` Lars Ingebrigtsen
2020-09-27 16:49 ` Eli Zaretskii
2020-09-28 13:16 ` Lars Ingebrigtsen
2020-09-28 13:43 ` Eli Zaretskii
2020-09-28 15:02 ` martin rudalics
2020-09-29 14:06 ` Eli Zaretskii [this message]
2020-09-29 14:09 ` Lars Ingebrigtsen
2020-09-29 14:22 ` Lars Ingebrigtsen
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=83a6x8lls7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43645@debbugs.gnu.org \
--cc=bluetrack121@gmail.com \
--cc=larsi@gnus.org \
--cc=rudalics@gmx.at \
/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).