rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: malte@TechFak.Uni-Bielefeld.DE
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: here strings
Date: Mon, 7 Jun 1993 04:42:08 -0400	[thread overview]
Message-ID: <9306070842.AA09937@idefix.techfak.uni-bielefeld.de> (raw)
In-Reply-To: Mail from 'John (Most modern computers would break if you stood on them) Mackin <john@civil.su.oz.au>' dated: 	Sat, 5 Jun 1993 08:55:54 -0400

So let me say I'm very sorry I didn't get the hint from your mail header:
"John (Most modern computers would break if you stood on them) Mackin".

But to all the non expert text tool users out there: The point is not all
tools deal correctly with non-newline terminated here strings. I spent
quite some time discovering this when I wrote a shell script that ran fine
with path = ( /vol/gnu/bin ... ) but didn't with path = ( /bin ... )
on a Sparc running SunOS 4 and another running SunOS 5.

	; /vol/gnu/bin/sed 's/a/e/g' <<< aaaaaa
	eeeeee
	; /bin/sed 's/a/e/g' <<< aaaaaa
	;

Because of this, I refuse to use here strings since their semantic is confusing
me and - if not avoidable - is replacable by "echo -n", unless someone can
show me a counter example.

I do not want to throw here strings out because that'll probably break a lot
of existing scripts. I'd just wanted to state their superfluousness.

Malte



       reply	other threads:[~1993-06-07  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <john@civil.su.oz.au>
1993-06-07  8:42 ` malte [this message]
1993-06-05 16:42 Alan Watson
  -- strict thread matches above, loose matches on Subject: below --
1993-06-05 12:53 malte
1993-06-05 12:55 ` John Mackin
1993-06-05 12:35 John Mackin

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=9306070842.AA09937@idefix.techfak.uni-bielefeld.de \
    --to=malte@techfak.uni-bielefeld.de \
    --cc=rc@hawkwind.utcs.toronto.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).