unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: bluetrack121@gmail.com, 43645@debbugs.gnu.org
Subject: bug#43645: 26.3; emacsclient -c does not open to correct window
Date: Sun, 27 Sep 2020 19:09:41 +0300	[thread overview]
Message-ID: <834knjnquy.fsf@gnu.org> (raw)
In-Reply-To: <87zh5byzr9.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  27 Sep 2020 18:02:02 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>,  43645@debbugs.gnu.org
> Date: Sun, 27 Sep 2020 18:02:02 +0200
> 
> I'm now sure what you mean by "the first emacsclient instance is on top
> also"?

My guess is that the frame created by the first emacsclient invocation
is on top (in the z-order) of that created by the second invocation.
That's probably a WM thing, though.

> When I do this, I get a new Emacs frame with the *scratch* buffer
> displayed

Does this happen even if the second invocation of emacsclient uses a
different file name, not the same test.txt as the first one?





  reply	other threads:[~2020-09-27 16:09 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 [this message]
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
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=834knjnquy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=43645@debbugs.gnu.org \
    --cc=bluetrack121@gmail.com \
    --cc=larsi@gnus.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).