From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 21132@debbugs.gnu.org, flitterio@gmail.com
Subject: bug#21132: 25.0.50; Emacs on Windows crashes evaluating x-frame-geometry in batch mode
Date: Sun, 26 Jul 2015 17:53:42 +0300 [thread overview]
Message-ID: <83si8bynpl.fsf@gnu.org> (raw)
In-Reply-To: <55B4C42C.8020205@gmx.at>
> Date: Sun, 26 Jul 2015 13:27:40 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: flitterio@gmail.com, 21132@debbugs.gnu.org
>
> >> And do we prefer (FRAME_W32_WINDOW (f) != 0) to (!FRAME_W32_WINDOW (f))?
> >
> > We prefer !FRAME_W32_P (f)
>
> x_set_foreground_color, x_set_background_color and x_set_mouse_color use
>
> if (FRAME_W32_WINDOW (f) != 0)
>
> Should these be changed?
No, I don't think so, because these are handlers for w32 frame
parameters, and I see no way they could be called from Lisp, except in
that context. Am I missing something?
> In x_change_tool_bar_height and w32_set_title_bar_text we use
>
> if (FRAME_W32_WINDOW (f))
>
> Should these be changed too?
No, for the same reasons.
> >> > I believe similar changes are needed in xfns.c and in nsfns.m, could
> >> > someone with access to the relevant OSes please check and apply?
> >>
> >> I'll look into these.
>
> I fixed these hopefully. The Gtk build always crashed when invoked with
> -nw so I now have `x-frame-geometry' return nil for terminal frames.
Thanks.
next prev parent reply other threads:[~2015-07-26 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 16:03 bug#21132: 25.0.50; Emacs on Windows crashes evaluating x-frame-geometry in batch mode Francis Litterio
2015-07-25 16:35 ` Eli Zaretskii
2015-07-25 18:17 ` martin rudalics
2015-07-25 18:53 ` Eli Zaretskii
2015-07-26 11:27 ` martin rudalics
2015-07-26 14:53 ` Eli Zaretskii [this message]
2015-07-27 16:02 ` martin rudalics
2015-07-27 16:25 ` Eli Zaretskii
2015-07-27 16:34 ` martin rudalics
2015-07-27 16:59 ` Eli Zaretskii
2015-08-24 8:17 ` martin rudalics
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=83si8bynpl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21132@debbugs.gnu.org \
--cc=flitterio@gmail.com \
--cc=rudalics@gmx.at \
/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).