unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathias Dahl <mathias.dahl@gmail.com>
To: emacs-devel@gnu.org
Subject: Could we include diff and grep (etc.) executables on Windows?
Date: Sun, 17 Nov 2019 12:50:19 +0100	[thread overview]
Message-ID: <CABrcCQ4i+FWH-WNLLNFcK=jiqgnfsFifE7ebC5wwGhvb9PgY7A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

Hi,

I sometimes help friends at work trying out Emacs. We're mostly on Windows
and one thing that makes things harder is that some of the useful features
of Emacs uses external tools. I'm thinking specifically about small
utilities like diff, grep, etc. So, on Windows, useful features like Ediff
and the different grep-based tools do not work out of the box.

I see that we bundle some exe files in the bin directory of Emacs (bunzip2,
bzcat, etc.), could we include some of the other core utilities as well?

Of course, if you commit to use Emacs you can make sure to install these
tools in one of several ways it can be done today (Cygwin. MSYS, natively
compiled, etc.) but users could be up and running much faster if they did
not have to do this. If you are trying out Emacs and compare it with other
editors today, where some of this are also built in but work without these
external tools, you might give up.

Any comments and opinions on this? Does anything stop us from bundling a
few more useful utilities to make Emacs even more useful by default? I
think it should benefit many users.

Thanks!

/Mathias

PS. Of course, Emacs has support for many external tools, and one might
ask: where do we stop? But, I think the core features, mentioned above, are
good candidates to include by default.

[-- Attachment #2: Type: text/html, Size: 1521 bytes --]

             reply	other threads:[~2019-11-17 11:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17 11:50 Mathias Dahl [this message]
2019-11-17 16:07 ` Could we include diff and grep (etc.) executables on Windows? Eli Zaretskii
2019-11-17 16:53 ` Stefan Monnier
2019-11-17 17:09   ` Eli Zaretskii
2019-11-17 17:49     ` Óscar Fuentes
2019-11-17 19:39       ` Stefan Monnier
2019-11-18 15:53         ` Phillip Lord
2019-11-18 18:05         ` Stephen Leake
2019-11-19 14:56           ` Phillip Lord
2019-11-19 15:43       ` Eli Zaretskii
2019-11-19 20:32         ` Óscar Fuentes
2019-11-20 16:11           ` Eli Zaretskii
2019-11-18 15:49     ` Phillip Lord
2019-11-18 16:08       ` Eli Zaretskii
2019-11-18 15:48 ` Phillip Lord
2019-11-18 16:09   ` Eli Zaretskii

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='CABrcCQ4i+FWH-WNLLNFcK=jiqgnfsFifE7ebC5wwGhvb9PgY7A@mail.gmail.com' \
    --to=mathias.dahl@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).