unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/windows-98 18e7a9f3d0c: Restore functionality on Windows 98
Date: Sun, 23 Jun 2024 06:36:58 -0700	[thread overview]
Message-ID: <CADwFkmn4pS8fmooSittnOvPrSaoRxUGoUf9g3HwOXnfQNK_L1w@mail.gmail.com> (raw)
In-Reply-To: <87h6dj24c7.fsf@yahoo.com>

Po Lu <luangruo@yahoo.com> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> In what state has the Windows 98 build been, and for how long?
>
> Please read last week's Windows 9X thread and the ChangeLog entry, where
> all this was elaborated upon at great length.
>
> Thanks.

Thanks, I read that, but it didn't answer my questions.

Let me try to reformulate what I'm asking:
- Is the Windows 98 build currently broken?
- How long has the Windows 98 build been broken?

These questions are important, because they will tell us something about
how much use this platform is seeing.  If it's been broken for 10+ years
and no users have noticed, then, well...

> Just remember that, whatever you should conclude, _there is no pretext
> on which to abandon support for Windows 98 to be had from this
> change_, or in the existing condition of NTEmacs.

Tempting as it is to propose that we abandon support for museum machines
(that should properly be running museum software), that's not my
intention here.  I'm merely trying to understand the state of Emacs as
it is now, and what we are planning to do.

At some point, we will abandon support for Windows 98 (and presumably
MS-DOS too) in modern Emacs.  Dropping such support will simplify
various parts of our codebase.  When that will happen is not really my
decision.  I think Eli is the one to say when we should pull the plug.



  reply	other threads:[~2024-06-23 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <171913140920.20405.14047614098587343624@vcs2.savannah.gnu.org>
     [not found] ` <20240623083013.0C544C1FB5B@vcs2.savannah.gnu.org>
2024-06-23 12:49   ` scratch/windows-98 18e7a9f3d0c: Restore functionality on Windows 98 Stefan Kangas
2024-06-23 13:09     ` Po Lu
2024-06-23 13:36       ` Stefan Kangas [this message]
2024-06-23 13:48         ` Eli Zaretskii
2024-06-23 14:04         ` Po Lu
2024-06-23 18:31           ` Stefan Kangas
     [not found]             ` <s54h6djp36w.fsf@yahoo.com>
2024-06-24 14:46               ` Po Lu

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=CADwFkmn4pS8fmooSittnOvPrSaoRxUGoUf9g3HwOXnfQNK_L1w@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --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 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).