all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
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 17:17:32 +0300	[thread overview]
Message-ID: <83r2nax8qr.fsf@gnu.org> (raw)
In-Reply-To: <87a7tyrpig.fsf@gmail.com> (message from Noam Postavsky on Fri, 20 Apr 2018 09:11:51 -0400)

> From: Noam Postavsky <npostavs@gmail.com>
> Cc: 31169@debbugs.gnu.org,  charliehemlock@gmail.com
> Date: Fri, 20 Apr 2018 09:11:51 -0400
> 
> 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.

So I guess we could simply fall back to the selected frame if no frame
is visible.  I wouldn't remove the test or fancy-splash-frame
entirely, because there could be several frames to choose from, and
this same code runs when the user invokes about-emacs in the middle of
a session.

> 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))

If we were removing the visibility test, yes.





  reply	other threads:[~2018-04-20 14:17 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
2018-04-20 14:17                     ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r2nax8qr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31169@debbugs.gnu.org \
    --cc=charliehemlock@gmail.com \
    --cc=npostavs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.