From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Windows 9X without KernelEx
Date: Sat, 15 Jun 2024 16:22:42 +0300 [thread overview]
Message-ID: <86ikyatk65.fsf@gnu.org> (raw)
In-Reply-To: <87msnm5p2q.fsf@yahoo.com> (message from Po Lu on Sat, 15 Jun 2024 21:10:37 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 15 Jun 2024 21:10:37 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Please reread what I wrote in previous messages, I think I explained
> > why we can expect usp10.dll to be available on any Windows 98 system
> > that is in actual use.
>
> So far as existing installations that we're aware of are concerned, this
> is true. Hence I'm not insisting on the Uniscribe change appearing in
> Emacs 30, but what is the harm in applying it to Emacs 31? By your own
> admission, Uniscribe is supposed to be obsolete, and the change will
> enables at least myself to test Emacs without being required to manage a
> private "DLL hell" or install Windoze Internet Exploder, whose Unix
> edition has already given me enough grief for a lifetime.
I'm not interested in complicating our code even a bit on behalf of
this non-problem.
next prev parent reply other threads:[~2024-06-15 13:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875xub8sn8.fsf.ref@yahoo.com>
2024-06-14 15:12 ` Windows 9X without KernelEx Po Lu via Emacs development discussions.
2024-06-14 15:26 ` Eli Zaretskii
2024-06-14 15:37 ` Po Lu
2024-06-14 16:06 ` Eli Zaretskii
2024-06-15 1:42 ` Po Lu
2024-06-15 2:42 ` Po Lu
2024-06-15 6:58 ` Eli Zaretskii
2024-06-15 7:12 ` Po Lu
2024-06-15 7:37 ` Eli Zaretskii
2024-06-15 7:45 ` Po Lu
2024-06-15 7:50 ` Eli Zaretskii
2024-06-15 9:39 ` Po Lu
2024-06-15 12:38 ` Eli Zaretskii
2024-06-15 13:10 ` Po Lu
2024-06-15 13:22 ` Eli Zaretskii [this message]
2024-06-15 13:31 ` Po Lu
2024-06-15 4:07 ` Stefan Kangas
2024-06-15 4:14 ` Po Lu
2024-06-15 4:45 ` Po Lu
2024-06-15 7:07 ` Eli Zaretskii
2024-06-15 7:22 ` Po Lu
2024-06-15 7:42 ` Eli Zaretskii
2024-06-15 9:35 ` Po Lu via Emacs development discussions.
2024-06-15 13:52 ` Eli Zaretskii
2024-06-15 14:18 ` Po Lu
2024-06-15 14:55 ` Eli Zaretskii
2024-06-15 15:15 ` Po Lu
2024-06-15 16:01 ` Eli Zaretskii
2024-06-16 2:01 ` Po Lu
2024-06-16 5:36 ` Eli Zaretskii
2024-06-16 5:50 ` Eli Zaretskii
2024-06-16 6:53 ` Po Lu
2024-06-16 11:34 ` Po Lu
2024-06-16 12:21 ` Eli Zaretskii
2024-06-23 8:35 ` Po Lu
2024-06-23 9:16 ` Eli Zaretskii
2024-06-23 20:25 ` Ken Brown
2024-06-24 2:30 ` Eli Zaretskii
2024-06-24 3:53 ` Po Lu
2024-06-25 19:20 ` Corwin Brust
2024-06-24 17:17 ` Ken Brown
2024-06-24 22:11 ` Ken Brown
2024-06-25 22:41 ` Ken Brown
2024-06-27 1:59 ` Po Lu
2024-06-27 13:18 ` Ken Brown
2024-06-27 13:42 ` Po Lu
2024-06-27 13:47 ` Po Lu
2024-06-27 14:52 ` Ken Brown
2024-06-30 2:07 ` Po Lu
2024-06-15 7:01 ` 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=86ikyatk65.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.