unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Cc: David Wardle <d.wardle.b@gmail.com>
Subject: Re: Suggested amendment to www.gnu.org/software/emacs/download.html#windows
Date: Sat, 09 Dec 2017 15:50:34 +0100	[thread overview]
Message-ID: <87609g7y6d.fsf@telefonica.net> (raw)
In-Reply-To: CABkDqSjbiBgc6pM_DJvBVePLaJKK1epOpDi6uV+Jam8OaQD4xw@mail.gmail.com

David Wardle <d.wardle.b@gmail.com> writes:

> I have edited the Wikipedia page:
> https://en.wikipedia.org/wiki/Comparison_of_file_comparison_tools
> ... to give readers some warning that, although Ediff can be used with
> Windows, it's currently not easy to install unless you have knowledge
> of using GNU software in a Windows environment.  I don't like doing
> this because it will obviously deter prospective Ediff (and hence
> Emacs users) (and, after I did finally manage to get Ediff working, I
> did find it useful).  However, I feel that it's only fair to give
> readers such a warning or they, like me, might end up wasting a lot of
> their time.  A better solution would be to make Ediff easier to
> install but I leave it with you.

The comparison table already says that Ediff will work on "anything with
Emacs and diff". Your warning is unnecesary and singles out a specific
platform.

Just because you took a long time to realize that Ediff requires diff it
doesn't mean that others will need redundant information about the fact.
Furthermore, that wikipedia page is not the best place to inform the
world about Ediff requirements. It would be much better if Ediff itself
emitted a message informing the user when diff is missing.




  reply	other threads:[~2017-12-09 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 21:24 Suggested amendment to www.gnu.org/software/emacs/download.html#windows David Wardle
2017-11-29  3:30 ` Eli Zaretskii
2017-12-09  5:09   ` David Wardle
2017-12-09 14:50     ` Óscar Fuentes [this message]
2017-12-09 14:59       ` 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

  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=87609g7y6d.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=d.wardle.b@gmail.com \
    --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).