From: Scott Merrilees <Sm@cerberus.bhpese.oz.au>
To: rc@archone.tamu.edu (The rc Mailing List)
Subject: Re: why i liked rc1.2's echo...
Date: Fri, 14 Feb 1992 06:26:46 -0600 [thread overview]
Message-ID: <199202140126.AA24097@cerberus.bhpese.oz.au> (raw)
> [or ``why i'm not letting the great echo controversy just die'']
Or you could do something I first heard espoused by Robert Elz
(kre@munnari), that echo should just echo its arguments, kind of like
a permanent -n.
So to get -n behavoiur, do
echo string
and to get normal echo behavoiur, use
echo 'string
'
This has that advantage that it is extremely simple & consistant.
Sm
next reply other threads:[~1992-02-14 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-02-14 12:26 Scott Merrilees [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-02-13 21:20 haahr
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=199202140126.AA24097@cerberus.bhpese.oz.au \
--to=sm@cerberus.bhpese.oz.au \
--cc=rc@archone.tamu.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).