From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27210@debbugs.gnu.org, ambrevar@gmail.com
Subject: bug#27210: 25.2; Recovering loaddefs.el with desktop-mode hangs when linum is on
Date: Sun, 04 Jun 2017 11:08:59 -0400 [thread overview]
Message-ID: <87efuzzt6c.fsf@users.sourceforge.net> (raw)
In-Reply-To: <837f0rc00d.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Jun 2017 17:15:14 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> And don't forget that the initial frame is invisible in non-daemon
> sessions as well, until some point during startup.
I don't understand, is this an objection? It only seems to support
making the daemon frame invisible as well (i.e., the approach in my
patch).
> There are more than 70 references to FRAME_VISIBLE_P in the C sources,
> and another 2 dozen references to frame-visible-p in Lisp sources --
> sounds to me like a lot of potential for breaking stuff.
>
> My alternative proposal is much simpler, is localized to linum.el, and
> in a nutshell tests exactly the same condition, since any frame in a
> daemon session that can be visible is by definition a client frame.
> Do you see any disadvantages with installing that instead?
The only disadvantage is that we still have this invisible daemon frame
which is marked as visible. I agree it's okay to apply your patch now
and see if we get some other similar problems later.
next prev parent reply other threads:[~2017-06-04 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 14:29 bug#27210: 25.2; Recovering loaddefs.el with desktop-mode hangs when linum is on Pierre Neidhardt
2017-06-03 14:56 ` Eli Zaretskii
2017-06-03 16:22 ` Pierre Neidhardt
2017-06-03 17:43 ` npostavs
2017-06-03 18:02 ` Eli Zaretskii
2017-06-03 18:38 ` Eli Zaretskii
2017-06-03 19:52 ` npostavs
2017-06-03 23:07 ` npostavs
2017-06-04 14:15 ` Eli Zaretskii
2017-06-04 15:08 ` npostavs [this message]
2017-06-04 16:31 ` 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=87efuzzt6c.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27210@debbugs.gnu.org \
--cc=ambrevar@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 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.