From: Eli Zaretskii <eliz@gnu.org>
To: Paul Moore <p.f.moore@gmail.com>
Cc: 23689@debbugs.gnu.org
Subject: bug#23689: Daemon-mode on Windows - "w32-initialized" is set too early
Date: Sat, 04 Jun 2016 13:58:20 +0300 [thread overview]
Message-ID: <83shwtusoj.fsf@gnu.org> (raw)
In-Reply-To: <CACac1F-+273k0kR3YjpsWoLgV+A=TD8cAmyDg8n6qgS+PBJAqA@mail.gmail.com> (message from Paul Moore on Sat, 4 Jun 2016 11:29:28 +0100)
> From: Paul Moore <p.f.moore@gmail.com>
> Date: Sat, 4 Jun 2016 11:29:28 +0100
> Cc: 23689@debbugs.gnu.org
>
> > It looks like this is an internal variable whose purpose is to make
> > sure the w32 GUI initialization code is called only once per session;
> > it shouldn't be used for any other purpose. I guess we could make
> > this more explicit in the doc string, but other than that I see no bug
> > here.
>
> OK. The spacemacs initialisation code uses this variable (along with
> ns-initialized and x-initialized) to ensure that certain actions (e.c.
> find-font) are only run after the display is initialized. It's only
> w32-initialized for which this approach doesn't work. Is there a
> better way of testing for this situation that should be used?
Frankly, I'm not sure what is the situation for which you want to
test. Can you describe the original problem in more detail?
next prev parent reply other threads:[~2016-06-04 10:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 10:33 bug#23689: Daemon-mode on Windows - "w32-initialized" is set too early Paul Moore
2016-06-04 10:07 ` Eli Zaretskii
2016-06-04 10:29 ` Paul Moore
2016-06-04 10:58 ` Eli Zaretskii [this message]
2016-06-04 12:54 ` Paul Moore
2016-06-04 15:01 ` Eli Zaretskii
2016-06-04 15:17 ` Paul Moore
2016-06-08 13:57 ` Paul Moore
2016-06-14 17:10 ` Eli Zaretskii
2016-06-14 18:20 ` Paul Moore
2016-06-14 18:55 ` Eli Zaretskii
2016-06-14 19:55 ` Paul Moore
2016-06-15 2:33 ` Eli Zaretskii
2016-06-15 7:08 ` Paul Moore
2016-06-15 11:11 ` Paul Moore
2016-06-15 14:55 ` Eli Zaretskii
2016-06-15 15:26 ` Paul Moore
2016-06-15 15:47 ` Eli Zaretskii
2016-06-15 16:58 ` Paul Moore
2019-11-02 1:07 ` Stefan Kangas
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=83shwtusoj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23689@debbugs.gnu.org \
--cc=p.f.moore@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).