From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>,
"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: Interest in nt_load_image?
Date: Tue, 31 Mar 2020 10:50:51 -0400 [thread overview]
Message-ID: <jwv1rp8lgxx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAAeL0SQWjwjM97dJvTAgLjU6-T_-fAJBVvemuR+6zdtO_3RRLQ@mail.gmail.com> (Juanma Barranquero's message of "Tue, 31 Mar 2020 15:14:01 +0200")
> We still want to support Windows 9X.
Do we? Do you know (of) someone using a recentish Emacs on Windows 9X?
>> We cannot do this at compile time, because we still try supporting
>> ancient Windows versions where GDI+ is not available. Moreover, I
>> think it's good to let users have the ability to decide dynamically
>> which image display capability they want. It certainly makes sense to
>> do that initially, while the GDI+ way is being tested in all kinds of
>> real-life use cases.
>> So all the compile-time tests will have to be rewritten as run-time
>> tests, and we should provide variables to force Emacs use/not use
>> GDI+, perhaps at image format granularity, and expose those variables
>> to Lisp, so users could control that.
>
> Did I misunderstand him?
Yes, he described the extra efforts that we should spend to try and
provide support for those hypothetical Windows 9X users out there.
I think that is very likely to be a waste, so I think we should first do
the easy thing and *if/when* someone comes complaining that it doesn't
work on Windows 9X then we can revisit this decision.
Stefan
next prev parent reply other threads:[~2020-03-31 14:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 19:33 Interest in nt_load_image? Juan José García-Ripoll
2020-03-29 21:55 ` Juan José García-Ripoll
2020-03-30 2:21 ` Eli Zaretskii
2020-03-30 7:54 ` Juan José García-Ripoll
2020-03-30 13:46 ` Eli Zaretskii
2020-03-30 14:36 ` Juan José García-Ripoll
2020-03-30 14:44 ` Juan José García-Ripoll
2020-03-30 15:50 ` Eli Zaretskii
2020-03-30 16:15 ` Juan José García-Ripoll
2020-03-30 16:37 ` Eli Zaretskii
2020-03-30 17:16 ` Stefan Monnier
2020-03-30 18:32 ` Eli Zaretskii
2020-03-30 18:41 ` Stefan Monnier
2020-03-30 18:57 ` Eli Zaretskii
2020-03-30 19:39 ` Stefan Monnier
2020-03-31 14:19 ` Eli Zaretskii
2020-03-30 18:06 ` Juan José García-Ripoll
2020-03-30 18:47 ` Eli Zaretskii
2020-03-30 18:53 ` Eli Zaretskii
2020-03-30 23:21 ` Juanma Barranquero
2020-03-31 8:01 ` Juan José García-Ripoll
2020-03-31 13:14 ` Juanma Barranquero
2020-03-31 14:50 ` Stefan Monnier [this message]
2020-03-31 15:25 ` Juanma Barranquero
2020-03-31 16:54 ` Stefan Monnier
2020-03-31 15:13 ` Juan José García-Ripoll
2020-03-31 15:28 ` Juanma Barranquero
2020-03-31 13:31 ` Eli Zaretskii
2020-03-30 15:14 ` Stefan Monnier
2020-03-30 15:57 ` Eli Zaretskii
2020-03-30 17:10 ` Stefan Monnier
2020-03-30 18:23 ` 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=jwv1rp8lgxx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=juanjose.garciaripoll@gmail.com \
--cc=lekktu@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).