unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 26995@debbugs.gnu.org
Subject: bug#26995: 26.0.50; emacsclient --tty FILE flashes previous frame's buffer before loading FILE
Date: Sat, 10 Feb 2018 12:35:35 +0200	[thread overview]
Message-ID: <83k1vl2kug.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48ww-F_MVyyZTfwD7=QzYYsv=88+Z8iRMyPCHeGmV+NQDg@mail.gmail.com> (message from Aaron Jensen on Mon, 5 Feb 2018 01:56:22 -0500)

> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Mon, 5 Feb 2018 01:56:22 -0500
> Cc: 26995@debbugs.gnu.org
> 
> Please see attached patch and let me know if this method is
> acceptable. It’s perhaps a little kludgy because sometimes a frame is
> created and sometimes it isn’t so we need both methods of ensuring the
> initial frame is set properly. This does appear to work for all
> scenarios I tested, however.

Thanks, this LGTM.  Please add ChangeLog-style commit log message for
the changes, and I will then push this to the master branch.





  parent reply	other threads:[~2018-02-10 10:35 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
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 [this message]
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=83k1vl2kug.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26995@debbugs.gnu.org \
    --cc=aaronjensen@gmail.com \
    /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).