From: Blue track <bluetrack121@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43645@debbugs.gnu.org
Subject: bug#43645: 26.3; emacsclient -c does not open to correct window
Date: Sun, 27 Sep 2020 20:36:05 +1000 [thread overview]
Message-ID: <CAJ-jD5pj=QZ+VHkQkwRjCNEntJsU-y1BBQ1UTEw-GGrTTsWNoQ@mail.gmail.com> (raw)
In-Reply-To: <83tuvjo82b.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Thanks for the response, it did not fix the issue. I hope this doesn't
sound condescending but did you follow the steps to reproduce? It's a weird
behaviour which I think is related to window splits:
```
emacs -Q --daemon
echo "Test" > test.txt
emacsclient -c test.txt
C-x 3
C-x b *scratch*
# In new terminal
emacsclient -c test.txt
# I get a new window with the *scratch* buffer, but under Ubuntu 20.04 the
first emacsclient instance is on top also
```
On Sun, 27 Sep 2020 at 19:58, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Blue track <bluetrack121@gmail.com>
> > Date: Sun, 27 Sep 2020 16:41:31 +1000
> >
> > When opening an emacsclient instance to a new intance of a buffer which
> > is already open, under some conditions it does not open to the correct
> > buffer.
>
> I think this problem was fixed in Emacs 27.1, so please upgrade and
> try again. If the problem persists, please tell the details.
>
> (I couldn't reproduce this in Emacs 27, FTR.)
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 1518 bytes --]
next prev parent reply other threads:[~2020-09-27 10:36 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 [this message]
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
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='CAJ-jD5pj=QZ+VHkQkwRjCNEntJsU-y1BBQ1UTEw-GGrTTsWNoQ@mail.gmail.com' \
--to=bluetrack121@gmail.com \
--cc=43645@debbugs.gnu.org \
--cc=eliz@gnu.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).