From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] echo -n
Date: Mon, 20 Nov 2006 15:59:21 +0100 [thread overview]
Message-ID: <200611201459.kAKExL908680@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Mon, 20 Nov 2006 14:41:22 +0000." <200611201441.aa18804@salmon.maths.tcd.ie>
> UNIX variants seem to vary (yes, I know, that's why they are called
> variants) in their behaviour. On FreeBSD and NetBSD echo -n | wc
> produces 0 0 0, agreeing with my intuition and the plan9 behaviour.
> On Solaris, on the other hand, echo -n | wc produces 1 1 3.
On my solaris (5.8) I see both behaviours, depending on the shell I use.
The 1 1 3 is produced by /usr/bin/echo.
its man page explains why we get this:
If any operand is "-n", it will be treated as a string, not
an option. The following character sequences will be
recognized within any of the arguments:
[...]
\c print line without new-line
[...]
USAGE
Portable applications should not use -n (as the first argu-
ment) or escape sequences.
; /usr/bin/echo '\c' |wc
0 0 0
;
Axel.
next prev parent reply other threads:[~2006-11-20 14:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 8:40 arisawa
2006-11-20 9:45 ` Martin Neubauer
2006-11-20 10:42 ` lucio
2006-11-20 17:35 ` maht
2006-11-20 12:46 ` Russ Cox
2006-11-20 14:41 ` John Stalker
2006-11-20 14:59 ` Dave Lukes
2006-11-20 14:59 ` Axel Belinfante [this message]
2006-11-20 15:34 ` ron minnich
2006-11-20 15:43 ` erik quanstrom
2006-11-20 16:37 ` Joel Salomon
2006-11-20 18:49 ` Russ Cox
2006-11-20 19:16 ` Francisco J Ballesteros
2006-11-20 19:57 ` Joel Salomon
2006-11-20 20:18 ` Federico Benavento
2006-11-20 20:38 ` Russ Cox
2006-11-20 21:00 ` Joel Salomon
2006-11-20 21:05 ` Francisco J Ballesteros
2006-11-20 21:55 ` Russ Cox
2006-11-20 22:11 ` Francisco J Ballesteros
2006-11-20 22:24 ` Martin Neubauer
2006-11-20 23:14 ` Gorka guardiola
2006-11-20 23:22 ` Francisco J Ballesteros
2006-11-20 23:57 ` Gorka guardiola
2006-11-21 3:24 ` lucio
2006-11-20 19:32 ` Joel Salomon
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=200611201459.kAKExL908680@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cse.psu.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.
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).