From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: MS-Windows build broken in Fmake_network_process
Date: Wed, 07 Apr 2010 09:59:07 +0200 [thread overview]
Message-ID: <871verith0.fsf@lola.goethe.zz> (raw)
In-Reply-To: E1NzLpO-0006lj-3F@fencepost.gnu.org
Richard Stallman <rms@gnu.org> writes:
> For that reason, people with some interest in the rights to their own
> computer may keep an older Windows installation around for software that
> can't run on free platforms. Usually off-net since Microsoft does no
> security updates to those versions.
>
> If there is a substantial pattern of running Emacs on Windows 9 on
> machines off the net, that means it would be useful to support Windows
> 9.
As I said, I doubt that the installations I am thinking of (like mine)
have need for a text editor.
It's probably more relevant that people may be running old systems in
the third world, and "upgrading" is not an option due to computing
resources and (non-OEM) operating system pricing (if people can be
bothered about the legality of their copies).
There probably are not many Emacs users on those systems either.
> We still have no commitment to support any nonfree operating system.
> The users who want this are welcome to work on it.
Well, I thought that the topic of _this_ discussion was at what time it
becomes ok to rip out existing support for older systems.
I have no idea. I was just countering the statement that there is no
use case for older Windows systems. With me, the licensing conditions
of newer systems (and their net-requiring phone-home functionality I
can't afford without the ability to do security updates) are
prohibitive. But my use cases indeed do not require Emacs.
--
David Kastrup
next prev parent reply other threads:[~2010-04-07 7:59 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 15:22 MS-Windows build broken in Fmake_network_process Eli Zaretskii
2010-03-26 15:48 ` Helmut Eller
2010-03-26 17:56 ` Eli Zaretskii
2010-03-26 18:05 ` Helmut Eller
2010-03-26 18:09 ` Eli Zaretskii
2010-03-26 18:17 ` Helmut Eller
2010-03-26 20:05 ` Eli Zaretskii
2010-03-26 21:14 ` Helmut Eller
2010-03-27 8:50 ` Eli Zaretskii
2010-03-27 10:09 ` Helmut Eller
2010-03-27 11:11 ` Eli Zaretskii
2010-03-27 13:56 ` Helmut Eller
2010-03-27 0:48 ` Chong Yidong
2010-03-27 7:42 ` Eli Zaretskii
2010-03-27 16:49 ` Jason Rumney
2010-03-27 16:55 ` Eli Zaretskii
2010-03-27 22:28 ` Christoph
2010-03-28 0:12 ` Florian Beck
2010-03-28 0:37 ` Óscar Fuentes
2010-03-28 7:26 ` Eli Zaretskii
2010-03-28 18:55 ` Chong Yidong
2010-03-28 20:10 ` Eli Zaretskii
2010-03-28 23:23 ` Jason Rumney
2010-03-29 23:39 ` Richard Stallman
2010-03-31 4:57 ` Stephen J. Turnbull
2010-03-31 8:38 ` Eli Zaretskii
2010-03-31 10:38 ` Juanma Barranquero
2010-03-31 11:19 ` Eli Zaretskii
2010-03-31 15:39 ` Stephen J. Turnbull
2010-03-31 16:39 ` Juanma Barranquero
2010-03-31 17:30 ` Stephen J. Turnbull
2010-03-31 17:36 ` Juanma Barranquero
2010-03-31 18:05 ` OT: (was: MS-Windows build broken in Fmake_network_process) Stefan Monnier
2010-03-31 15:28 ` MS-Windows build broken in Fmake_network_process Stephen J. Turnbull
2010-03-31 16:12 ` Eli Zaretskii
2010-03-31 16:59 ` Stephen J. Turnbull
2010-03-31 17:27 ` Eli Zaretskii
2010-03-31 18:08 ` Stephen J. Turnbull
2010-04-06 7:50 ` David Kastrup
2010-04-07 3:21 ` Richard Stallman
2010-04-07 7:59 ` David Kastrup [this message]
2010-03-28 0:39 ` Christoph
2010-03-28 7:21 ` Windows 9X compatibility Eli Zaretskii
2010-03-28 14:59 ` Óscar Fuentes
2010-03-28 15:24 ` Lennart Borgman
2010-03-28 15:56 ` Eli Zaretskii
2010-03-28 16:09 ` Juanma Barranquero
2010-03-28 18:03 ` joakim
2010-03-29 23:39 ` Richard Stallman
2010-03-28 19:57 ` Óscar Fuentes
2010-03-28 20:32 ` Eli Zaretskii
2010-03-28 22:26 ` Juanma Barranquero
2010-03-28 19:27 ` Christoph
2010-03-28 20:18 ` Eli Zaretskii
2010-03-28 21:04 ` Christoph
2010-03-28 7:17 ` Windows 9X compatibility (was: MS-Windows build broken in Fmake_network_process) Eli Zaretskii
2010-03-28 7:33 ` MS-Windows build broken in Fmake_network_process Jason Rumney
2010-03-28 8:12 ` Eli Zaretskii
2010-03-29 23:39 ` Richard Stallman
2010-03-28 9:11 ` Serious performance problem with process output on Mac OSX Christian Lynbech
2010-03-28 14:41 ` Adrian Robert
2010-03-29 21:58 ` Adrian Robert
2010-03-29 23:26 ` David Reitter
2010-03-29 23:54 ` Chong Yidong
2010-03-30 7:43 ` Adrian Robert
2010-03-30 13:05 ` David Reitter
2010-03-30 17:39 ` Jimmy Yuen Ho Wong
2010-03-30 17:47 ` Chong Yidong
2010-03-31 2:38 ` Jimmy Yuen Ho Wong
2010-03-31 4:00 ` Chong Yidong
2010-03-31 13:41 ` Jimmy Yuen Ho Wong
2010-03-31 14:28 ` Chong Yidong
2010-03-31 14:29 ` Adrian Robert
2010-03-29 23:48 ` MS-Windows build broken in Fmake_network_process Davis Herring
2010-03-30 5:41 ` Jason Rumney
2010-03-26 23:03 ` Juanma Barranquero
2010-03-27 0:51 ` YAMAMOTO Mitsuharu
2010-03-27 8:44 ` Eli Zaretskii
2010-03-27 13:01 ` Óscar Fuentes
2010-03-27 13:18 ` Juanma Barranquero
2010-03-28 17:29 ` Kim F. Storm
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=871verith0.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/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).