all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: system-type
Date: Sat, 21 Mar 2009 14:59:46 -0400	[thread overview]
Message-ID: <jwvtz5mvh4t.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <uab7foso1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 Mar 2009 16:29:50 +0200")

>> > The text sounds as if this is exhaustive list, but then what is the
>> > value defined by the NextSTEP port?
>> Depends: if it's running under Mac OS X, it'll be `darwin', if it's
>> running under GNU/Linux it'll be `gnu/linux', ...
> `darwin' is not in that list.  Should it be added?

Yes.  It's in the docstring.

> Also, what with all the other Unixoid systems (which I presume we
> still support), like *BSD, Solaris, etc.?

As the docstring explains: "Anything else indicates some sort of
Unix system."

>> > If `system-type' is not the way
>> > to distinguish the NextSTEP port from other platforms, then what is?
>> window-system?
> That would fail under -nw, I think.  I used `(featurep 'ns)', which
> works, according to David Reitter.

Under -nw you shouldn't have to (need to) worry about nextstep.
At least, it seems no different than it was with Carbon before (or with
X11, ...).


        Stefan




  reply	other threads:[~2009-03-21 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21  9:51 system-type Eli Zaretskii
2009-03-21 13:58 ` system-type Stefan Monnier
2009-03-21 14:29   ` system-type Eli Zaretskii
2009-03-21 18:59     ` Stefan Monnier [this message]
2009-03-21 20:21       ` system-type Eli Zaretskii
2009-03-21 21:04         ` system-type Stefan Monnier
2009-03-27 14:52       ` system-type Eli Zaretskii
2009-03-27 14:57         ` system-type Eli Zaretskii
2009-03-27 16:25         ` system-type Stefan Monnier

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=jwvtz5mvh4t.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@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.