From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: jbuehler@hekimian.com, emacs-devel@gnu.org
Subject: Re: [PATCHES] patches for compiling GNU emacs 21.2 under Cygwin
Date: Wed, 4 Dec 2002 16:25:48 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1021204162419.5872B-100000@is> (raw)
In-Reply-To: <E18JXNH-0003zI-00@fencepost.gnu.org>
On Wed, 4 Dec 2002, Richard Stallman wrote:
> Making a new value for system-type is a drastic thing to do.
> It could mean many places that test system-type need to be changed.
> Is that really the best thing to do here? How many of these tests
> want to treat cygwin differently from windows-nt, and how many of
> them want to treat it the same?
Actually, I'd expect the Cygwin build be very close to the Unix and GNU
systems, not to windows-nt. But there are, at least in principle, cases
where they will need to do something Windowsish, like with
case-sensitivity in file names.
next prev parent reply other threads:[~2002-12-04 14:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <amvm2v$l11$1@main.gmane.org>
2002-11-27 17:43 ` [PATCHES] patches for compiling GNU emacs 21.2 under Cygwin Eli Zaretskii
2002-11-28 8:01 ` Roman Belenov
2002-11-28 17:13 ` Eli Zaretskii
2002-11-29 5:57 ` Roman Belenov
2002-12-02 16:13 ` Stefan Monnier
2002-12-02 18:18 ` Eli Zaretskii
2002-12-02 19:21 ` Stefan Monnier
2002-12-02 20:36 ` Jason Rumney
2002-12-03 5:50 ` Eli Zaretskii
2002-12-03 14:17 ` Joe Buehler
2002-12-03 14:14 ` Joe Buehler
2002-12-03 16:37 ` Joe Buehler
2002-12-03 18:24 ` Eli Zaretskii
2002-12-03 18:21 ` Eli Zaretskii
2002-12-04 7:39 ` Roman Belenov
2002-12-03 23:16 ` Kim F. Storm
2002-12-04 11:07 ` Richard Stallman
2002-12-04 11:07 ` Richard Stallman
2002-12-04 14:25 ` Eli Zaretskii [this message]
2002-12-04 18:39 ` Joe Buehler
2002-12-05 6:02 ` Eli Zaretskii
2002-12-06 13:31 ` Richard Stallman
2002-12-07 19:04 ` Eli Zaretskii
[not found] <E18LD00-0004Ov-00@fencepost.gnu.org>
2002-12-09 6:12 ` Eli Zaretskii
2002-12-09 14:57 ` Joe Buehler
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=Pine.SUN.3.91.1021204162419.5872B-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=jbuehler@hekimian.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.
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).