Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!hp4nl!botter!star.cs.vu.nl!maart
From: maart@cs.vu.nl (Maarten Litmaath)
Newsgroups: comp.unix.questions
Subject: Re^2: Vi
Message-ID: <2731@piraat.cs.vu.nl>
Date: 12 Jun 89 19:03:07 GMT
References: <19890@adm.BRL.MIL> <13816@dartvax.Dartmouth.EDU> <1128@vsi.COM> <1042@philmds.UUCP>
Organization: V.U. Informatica, Amsterdam, the Netherlands
Lines: 29

leo@philmds.UUCP (Leo de Wit) writes:
\...
\#! /bin/sed -f
\...
\	s/\(\n\)\([^	][^	][^	][^	][^	]\)	/\2   \1/
\...
\/......................................................................../!{
\...

Leo's sed `solution' makes 2 things clear:

	1) sed ought to have C escape sequences like '\t'
	2) sed ought to have some kind of `run' specifier
	   - quick: how many dots did Leo put on the `/<dots>/!{' line?

Ad 1: one should AVOID putting a HARD TAB in human-readable code, where using
the APPROPRIATE NUMBER OF SPACES would NOT have the SAME EFFECT.
Indentation: OK.
Example: in shell scripts use

	tab=`ctrl I`
	..."$tab"...

instead of

	..."	"...
-- 
"I HATE arbitrary limits, especially when |Maarten Litmaath @ VU Amsterdam:
   they're small."  (Stephen Savitzky)    |maart@cs.vu.nl, mcvax!botter!maart