all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Windows emacs-25.1 i686 vs x86_64?
Date: Sun, 06 Nov 2016 21:50:49 +0000	[thread overview]
Message-ID: <877f8gqnuu.fsf@russet.org.uk> (raw)
In-Reply-To: <831sypjmst.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 06 Nov 2016 05:43:14 +0200")

Eli Zaretskii <eliz@gnu.org> writes:
>> > Also, please don't remove information about Windows 9X, as the 32-bit
>> > MS-Windows build of Emacs still supports that.
>> 
>> I would argue against this. I removed the material on Windows 9x since
>> it has long since reached EOL -- 10 years, or 25% of Emacs' existance.
>
> That is true, but we still try supporting those old systems, as they
> are widespread in the 3rd world.  We have code whose only purpose is
> to continue that support.  We don' take MS EOL decisions as important.

EOL decisions are important. Of course, this does not mean that you have
to take them as gospel, but to ignore them is not a good course, I
think.

Still I see others have taken up this issue in the thread, so I will not
revisit the issue of whether 95/98 are supported further, and so only
comment on it's position in the documentation.

>> While providing this information somewhere might be useful, having it in
>> this readme mostly serves to make the readme and to some extent Emacs
>> appear unmaintained.
>
> I don't see why a document that mentions the latest version of Emacs
> could appear unmaintained.  If you'd like we could mention the date of
> last update in the file.


I think that this is not the issue -- in general, if I read a document
that has lots of advice on what to do with long obsolete operating
systems, I would just assume that it has not been maintained.


>> In addition, it also makes the documentation longer which adds to
>> the impression that Emacs is hard to use.
>
> One short paragraph is not a significant addition, IMO.


The file is already very long for a readme. My experience of watching
new Emacs users is that there experience is very much "do I have to read
all of this to edit a file".

Reducing things like this readme to an absolute minimum seems a useful
aim. How to support a very, very old operating system seems a poor thing
to include. To steal a quote "It's a beautiful thing, the Destruction of
words."

Incidentally, on this topic, is this paragraph (adding in 2001) still at
all relevant?

  Virus scanners

  Some virus scanners interfere with Emacs' use of subprocesses.  If you
  are unable to use subprocesses and you use Dr. Solomon's WinGuard or
  McAfee's Vshield, turn off "Scan all files" (WinGuard) or "boot sector
  scanning" (McAfee exclusion properties).


>> I'd be happy to look for somewhere else to put this information, if you
>> think it need to be retained.
>
> There's no other good place.  This is the file where users should look
> for preliminaries for Emacs installation.


README.W32.obsolete?

Phil



  parent reply	other threads:[~2016-11-06 21:50 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 15:32 Windows emacs-25.1 i686 vs x86_64? David M. Miller
2016-11-03 15:39 ` tomas
2016-11-03 16:00 ` David M. Miller
2016-11-03 16:26   ` John Mastro
2016-11-03 16:28   ` Phillip Lord
2016-11-03 17:44     ` David M. Miller
2016-11-03 22:21       ` Phillip Lord
2016-11-03 17:58     ` Eli Zaretskii
2016-11-03 22:25       ` Phillip Lord
2016-11-04  7:19         ` Eli Zaretskii
2016-11-04 10:19           ` Phillip Lord
2016-11-05  8:16             ` Eli Zaretskii
2016-11-05 22:26               ` Phillip Lord
2016-11-06  3:43                 ` Eli Zaretskii
2016-11-06  8:10                   ` Paul Eggert
2016-11-06 15:48                     ` Eli Zaretskii
2016-11-06 16:13                       ` Óscar Fuentes
2016-11-06 16:43                         ` Eli Zaretskii
2016-11-06 17:01                           ` Óscar Fuentes
2016-11-06 17:24                             ` Eli Zaretskii
2016-11-06 18:26                               ` Óscar Fuentes
2016-11-06 18:42                                 ` Eli Zaretskii
2016-11-06 19:17                                 ` Eli Zaretskii
2016-11-06 20:15                                   ` Óscar Fuentes
2016-11-07 14:40                             ` Richard Stallman
2016-11-07 15:16                               ` Phillip Lord
2016-11-08 13:53                                 ` Richard Stallman
2016-11-06 16:51                       ` Stefan Monnier
2016-11-06 18:50                       ` John Wiegley
2016-11-07 14:42                         ` Richard Stallman
2016-11-06 21:54                       ` Paul Eggert
2016-11-06 21:57                         ` Daniel Colascione
2016-11-07 14:43                         ` Richard Stallman
2016-11-07 15:15                           ` Daniel Colascione
2016-11-07 15:26                           ` Phillip Lord
2016-11-08 13:53                             ` Richard Stallman
2016-11-08 14:52                               ` Phillip Lord
2016-11-08 15:31                                 ` Eli Zaretskii
2016-11-09 16:50                                   ` Phillip Lord
2016-11-09 17:15                                     ` Eli Zaretskii
2016-11-09 17:18                                     ` Stefan Monnier
2016-11-10 15:19                                       ` Phillip Lord
2016-11-09  7:00                                 ` martin rudalics
2016-11-15 10:26                                 ` Phillip Lord
2016-11-07 16:34                           ` Paul Eggert
2016-11-07 18:07                             ` Eli Zaretskii
2016-11-07 19:02                               ` Perry E. Metzger
2016-11-07 19:29                                 ` Eli Zaretskii
2016-11-07 21:54                                   ` Phillip Lord
2016-11-07 19:39                                 ` Stefan Monnier
2016-11-07 20:02                                   ` Perry E. Metzger
2016-11-07 20:10                                     ` Stefan Monnier
2016-11-07 20:22                                       ` Perry E. Metzger
2016-11-07 20:27                                         ` Eli Zaretskii
2016-11-08  3:48                                           ` Elias Mårtenson
2016-11-08 15:32                                             ` Eli Zaretskii
2016-11-07 18:49                           ` Perry E. Metzger
2016-11-08 13:55                             ` Richard Stallman
2016-11-08 14:34                               ` Perry E. Metzger
2016-11-06 21:50                   ` Phillip Lord [this message]
2016-11-06  4:13                 ` Noam Postavsky

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=877f8gqnuu.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eliz@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 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.