From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Best way to run on Windows XP
Date: Mon, 25 Jul 2005 21:35:23 +0300 [thread overview]
Message-ID: <uhdeiivis.fsf@gnu.org> (raw)
In-Reply-To: <200507251405.j6PE5hf2022073@beta.mvs.co.il> (ehud@unix.mvs.co.il)
> Date: Mon, 25 Jul 2005 17:05:43 +0300
> From: "Ehud Karni" <ehud@unix.mvs.co.il>
> Cc: help-gnu-emacs@gnu.org
>
> Cygwin Emacs is VERY well maintained by Joe Buehler.
Still, his last ChangeLog entry in the Emacs CVS dates back to April
2004. If the Cygwin port is still in good shape, it's probably by
sheer luck (or by work of others).
> I was working with NTEmacs and switched to the Cygwin Emacs because
> of two reasons:
> 1. You have the full UNIX toolset with real POSIX support
> (e.g. same paths, env vars with lower case letters).
You can have the same with GnuWin32.
> 2. Some things that were included in UNIX Emacs (jpeg IIRC) were not
> supported by the NTEmacs but worked with Cygwin Emacs on X.
This is supported in the CVS NTEmacs code for a very long time (before
the Cygwin support became part of the CVS).
So I think now Cygwin and NTEmacs basically work equally well, and the
choice depends on whether one wants a native Windows Emacs or a
Posix-compliant Emacs.
next prev parent reply other threads:[~2005-07-25 18:35 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
2005-07-25 14:05 ` Best " Ehud Karni
2005-07-25 18:35 ` Eli Zaretskii [this message]
[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=uhdeiivis.fsf@gnu.org \
--to=eliz@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.
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).