From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26995@debbugs.gnu.org
Subject: bug#26995: 26.0.50; emacsclient --tty FILE flashes previous frame's buffer before loading FILE
Date: Fri, 19 May 2017 08:44:03 -0700 [thread overview]
Message-ID: <m21srksvgc.fsf@gmail.com> (raw)
In-Reply-To: <83bmqo3lv9.fsf@gnu.org>
Eli Zaretskii writes:
> I can indeed reproduce the described behavior, but I see the same in
> Emacs 25.2 and in Emacs 24.5. The reason is simple: the way server.el
> is written, we first create the client frame, and only then show the
> file there. So the frame is created with no file to visit, and Emacs
> always shows the last buffer in the new frame in those cases.
I see, so not a bug then. Is it possible to (easily) improve its behavior? It's not a big enough deal to warrant spending a lot of time on, I don't think.
>
> Maybe your workaround worked for Emacs 25, but no longer works with
> Emacs 26?
Perhaps, or maybe I was seeing an even bigger flash because persp-mode was restoring an entire perspective before. For reference, here is the original issue and the fix/workaround I ended up on:
https://github.com/Bad-ptr/persp-mode.el/issues/64
--
Aaron
next prev parent reply other threads:[~2017-05-19 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 14:28 bug#26995: 26.0.50; emacsclient --tty FILE flashes previous frame's buffer before loading FILE Aaron Jensen
2017-05-19 15:30 ` Eli Zaretskii
2017-05-19 15:44 ` Aaron Jensen [this message]
2017-05-19 17:27 ` Eli Zaretskii
2018-02-05 6:56 ` Aaron Jensen
2018-02-09 21:06 ` Aaron Jensen
2018-02-10 10:35 ` Eli Zaretskii
2018-02-10 16:56 ` Aaron Jensen
2018-02-16 15:45 ` Eli Zaretskii
2019-11-01 13:56 ` Eli Zaretskii
2019-11-01 16:27 ` Aaron Jensen
2019-11-01 17:00 ` Eli Zaretskii
2019-11-07 17:15 ` Eli Zaretskii
2022-04-17 19:50 ` Lars Ingebrigtsen
2022-04-17 22:55 ` Aaron Jensen
2022-04-18 9:07 ` 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=m21srksvgc.fsf@gmail.com \
--to=aaronjensen@gmail.com \
--cc=26995@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).