From: Zefram <A.Main@dcs.warwick.ac.uk>
To: schaefer@nbn.com
Cc: zsh-workers@math.gatech.edu
Subject: Re: Sigh. Wouldn't consistency be nice?
Date: Sat, 29 Jun 1996 17:41:07 +0100 (BST) [thread overview]
Message-ID: <2092.199606291641@tamarind.dcs.warwick.ac.uk> (raw)
In-Reply-To: <960629092455.ZM5050@candle.brasslantern.com> from "Bart Schaefer" at Jun 29, 96 09:24:53 am
>bash% echo `hostname` $HOSTTYPE
>zagzig i386
>
>tcsh% echo `hostname` $HOSTTYPE
>zagzig i486-linux
>
>zsh% echo `hostname` $MACHTYPE $OSTYPE
>zagzig i586 linux
Thus conclusively proving that zsh is superior, because its knowledge
of the CPU type is more specific.
(Yes, consistency would be nice. And I'm surprised that bash, being a
GNU program, didn't produce the same answer as zsh, which gets it from
autoconf.)
-zefram
next prev parent reply other threads:[~1996-06-29 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-29 16:24 Bart Schaefer
1996-06-29 16:41 ` Zefram [this message]
1996-06-29 17:53 ` Hrvoje Niksic
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=2092.199606291641@tamarind.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).