From: jasonr (Jason Rumney) @ f2s.com
Subject: Re: "Best" way to run on Windows XP
Date: Sun, 24 Jul 2005 17:51:40 +0100 [thread overview]
Message-ID: <u4qak171f.fsf@jasonrumney.net> (raw)
In-Reply-To: 1122221022.525785.237790@g43g2000cwa.googlegroups.com
"Chris Lott" <Chris.Lott@gmail.com> writes:
> Is the "best" way to run emacs on Windows XP to use the Native XP build
> or the Cygwin? By "best" I mean: stable, able to run elisp code from
> emacs.sources, and able to effectively use external tools like grep,
> diff, etc... ?
If you are only using Cygwin tools, then Cygwin might be better in
some respects, but if that is the case, why use Windows at all?
For any other case, I'd have to say the native build for the following
reasons.
Cygwin Emacs does not appear to be regularly maintained. Maybe the
original port was good enough that it doesn't need anyone maintaining
it, but I doubt it.
A lot of effort has been put into making native Windows Emacs work
with Cygwin tools. The cygwin developers don't seem to show any
interest in making their tools work with native Windows tools. Even
for such programs as make where running external tools is the
program's primary purpose, their solution is to ask everyone to
rewrite their makefiles with awkward macros around filename arguments
that might be processed by non-Cygwin tools.
next prev parent reply other threads:[~2005-07-24 16:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 16:03 "Best" way to run on Windows XP Chris Lott
2005-07-24 16:20 ` Chris L
2005-07-24 18:58 ` Eli Zaretskii
2005-07-24 19:46 ` Peter Dyballa
2005-07-25 3:23 ` Eli Zaretskii
[not found] ` <mailman.1549.1122262220.20277.help-gnu-emacs@gnu.org>
2005-07-25 7:25 ` David Kastrup
2005-07-25 19:00 ` Eli Zaretskii
[not found] ` <mailman.1677.1122318926.20277.help-gnu-emacs@gnu.org>
2005-07-25 19:31 ` David Kastrup
2005-07-26 5:07 ` Eli Zaretskii
[not found] ` <mailman.1714.1122355790.20277.help-gnu-emacs@gnu.org>
2005-07-26 8:49 ` David Kastrup
2005-07-26 18:15 ` Eli Zaretskii
[not found] ` <mailman.1511.1122231867.20277.help-gnu-emacs@gnu.org>
2005-07-25 17:49 ` Klaus Berndl
2005-07-24 16:47 ` David Kastrup
2005-07-24 19:01 ` Eli Zaretskii
2005-07-24 21:14 ` Lennart Borgman
[not found] ` <mailman.1513.1122231961.20277.help-gnu-emacs@gnu.org>
2005-07-25 17:50 ` Klaus Berndl
2005-07-24 16:51 ` Jason Rumney [this message]
2005-07-25 14:05 ` Best " Ehud Karni
2005-07-25 18:35 ` Eli Zaretskii
[not found] ` <mailman.1610.1122300590.20277.help-gnu-emacs@gnu.org>
2005-07-25 17:54 ` Klaus Berndl
2005-07-25 18:41 ` Eli Zaretskii
2005-07-25 19:04 ` J. David Boyd
2005-07-26 4:55 ` Eli Zaretskii
[not found] ` <mailman.1712.1122353968.20277.help-gnu-emacs@gnu.org>
2005-07-28 13:57 ` Klaus Berndl
2005-07-24 18:56 ` "Best" " Eli Zaretskii
2005-07-24 19:08 ` Drew Adams
2005-07-25 16:50 ` Jason Dufair
2005-07-25 22:20 ` Peter Lee
2005-08-16 22:07 ` treebeard
2005-08-16 22:26 ` Lennart Borgman
2005-08-18 1:55 ` Brett Kelly
2005-10-15 8:16 ` Eli Zaretskii
[not found] ` <mailman.4126.1124331117.20277.help-gnu-emacs@gnu.org>
2005-08-25 1:02 ` David Combs
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=u4qak171f.fsf@jasonrumney.net \
--to=jasonr@f2s.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).