From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31169@debbugs.gnu.org, charliehemlock@gmail.com
Subject: bug#31169: 26.1; Emacs 26.1 RC1 (gtk) display issues over SSH/X11 with xming/vcxsrv
Date: Fri, 20 Apr 2018 09:11:51 -0400 [thread overview]
Message-ID: <87a7tyrpig.fsf@gmail.com> (raw)
In-Reply-To: <83tvs6xc4h.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Apr 2018 16:04:30 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Ah, `fancy-splash-frame' checks `frame-visible-p', which, for my window
>> manager, depends on when I switch to the workspace.
>
> Is that a necessary test? What happens if you use the selected frame,
> when no frame is found to be visible?
Seems to be unnecessary: if I comment out the frame-visible-p check, I
get the fancy splash regardless of when I switch workspace, and I see no
bad side effects.
Maybe that means this part would also be unneeded:
(defun fancy-splash-frame ()
[...]
;; MS-Windows needs this to have a chance to make the initial
;; frame visible.
(if (eq (window-system) 'w32)
(sit-for 0 t))
next prev parent reply other threads:[~2018-04-20 13:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 0:09 bug#31169: 26.1; Emacs 26.1 RC1 (gtk) display issues over SSH/X11 with xming/vcxsrv charlie hemlock
2018-04-16 17:40 ` Eli Zaretskii
2018-04-16 23:37 ` charlie hemlock
2018-04-17 2:34 ` Eli Zaretskii
2018-04-18 0:30 ` charlie hemlock
2018-04-18 13:20 ` Eli Zaretskii
2018-04-19 0:58 ` charlie hemlock
2018-04-19 0:42 ` Noam Postavsky
2018-04-19 1:18 ` charlie hemlock
2018-04-19 1:27 ` Noam Postavsky
2018-04-19 6:47 ` Eli Zaretskii
2018-04-19 23:41 ` charlie hemlock
2018-04-20 0:06 ` Noam Postavsky
2018-04-20 6:54 ` Eli Zaretskii
2018-04-20 12:05 ` Noam Postavsky
2018-04-20 13:04 ` Eli Zaretskii
2018-04-20 13:11 ` Noam Postavsky [this message]
2018-04-20 14:17 ` Eli Zaretskii
2018-06-19 0:16 ` Noam Postavsky
2018-04-19 6:43 ` Eli Zaretskii
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=87a7tyrpig.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31169@debbugs.gnu.org \
--cc=charliehemlock@gmail.com \
--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).