From: Dan Harkless <dan.harkless@gmail.com>
To: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Subject: Re: [HEADSUP] Phasing out old Windows versions and 32 bit support [XEmacs for 64-bit?]
Date: Wed, 27 Oct 2021 15:35:07 -0700 [thread overview]
Message-ID: <83c8f0a3-59ff-493b-19e4-27ce078cf806@gmail.com> (raw)
In-Reply-To: <YXhrJUHpQ+VvO8Xj@calimero.vinschen.de>
On 10/26/2021 1:55 PM, Corinna Vinschen via Cygwin wrote:
> We're also planning to drop Support for the 32 bit release of Cygwin in
> 2022, thus Cygwin 3.4.0 won't come in 32 bit anymore, and the package
> maintainers won't have to update 32 bit packages anymore. If you're
> still running Cygwin under WOW64, consider to move to 64 bit in the next
> couple of months.
Except for my 32-bit Windows 7 (upgraded to 8.1) netbook, the only
reason I still install Cygwin32 in parallel with Cygwin64 is so I can
install the XEmacs packages. Anyone know more about the difficulty in
getting those packages to work on 64-bit? XEmacs from EPEL works fine
on 64-bit Linux, FWIW.
From past attempts, I know it would take far too much time (and Elisp
programming) to get GNU Emacs up to the usability level that I've had
XEmacs at since the '90s.
(w3m-img is another package only available on Cygwin32 that I install,
but I don't use it and am not concerned about that one.)
Thanks,
Dan Harkless
next prev parent reply other threads:[~2021-10-27 22:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 20:55 [HEADSUP] Phasing out old Windows versions and 32 bit support Corinna Vinschen
2021-10-26 22:01 ` [QUAR] " Eliot Moss
2021-10-26 22:52 ` Michel LaBarre
2021-10-27 4:29 ` Peter A. Castro
2021-10-27 8:53 ` Corinna Vinschen
2021-10-27 16:28 ` Peter A. Castro
2021-10-28 7:00 ` Corinna Vinschen
2021-10-27 14:57 ` Michel LaBarre
2021-10-27 16:38 ` Peter A. Castro
2021-10-27 8:33 ` Corinna Vinschen
2021-10-27 0:24 ` Takashi Yano
2021-10-27 8:49 ` Corinna Vinschen
2021-10-27 9:37 ` Thomas Wolff
2021-10-27 10:20 ` Corinna Vinschen
2021-10-27 16:46 ` Peter A. Castro
2021-10-27 21:04 ` Thomas Wolff
2021-10-27 23:35 ` Peter A. Castro
2021-10-27 13:07 ` Andrew Schulman
2021-10-27 11:03 ` L A Walsh
2021-10-27 11:10 ` Corinna Vinschen
2021-10-27 15:25 ` [HEADSUP] " Jim Reisert AD1C
2021-10-27 17:22 ` EXTERNAL: " Damon Register
2021-10-27 22:35 ` Dan Harkless [this message]
2021-10-27 22:37 ` [HEADSUP] Phasing out old Windows versions and 32 bit support [XEmacs for 64-bit?] Dan Harkless
2021-10-27 22:36 ` Dan Harkless
2021-10-28 8:47 ` Henry S. Thompson
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=83c8f0a3-59ff-493b-19e4-27ce078cf806@gmail.com \
--to=dan.harkless@gmail.com \
--cc=cygwin@cygwin.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.
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).