From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCHES] patches for compiling GNU emacs 21.2 under Cygwin
Date: Wed, 04 Dec 2002 06:07:27 -0500 [thread overview]
Message-ID: <E18JXNH-0003zI-00@fencepost.gnu.org> (raw)
In-Reply-To: <asie31$nnk$1@main.gmane.org> (message from Joe Buehler on Tue, 03 Dec 2002 09:14:05 -0500)
> - (if (memq system-type '(hpux dgux usg-unix-v irix linux gnu/linux))
> + (if (memq system-type '(hpux dgux usg-unix-v irix linux gnu/linux cygwin))
>
> Since we are introducing a new value for system-type, it should be
> documented in the ELisp manual, I think.
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?
Is it possible to distinguish them using system-configuration?
next prev parent reply other threads:[~2002-12-04 11:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 19:10 [PATCHES] patches for compiling GNU emacs 21.2 under Cygwin Joe Buehler
2002-11-27 17:43 ` 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 [this message]
2002-12-04 14:25 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E18JXNH-0003zI-00@fencepost.gnu.org \
--to=rms@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.