On Fri, 24 Oct 1997 09:59:43 +0100 (WET DST),
"J. Daniel Smith" <J(_dot_)Daniel(_dot_)Smith(_at_)WriteMe(_dot_)com> wrote:
era eriksson writes on 23 October 1997 at 21:03:52
Like I said in a different message, I would never actively promote an
i flag other than when the user sees unwanted warnings in the log file
(and even then, how do you know they're unwanted?)
| head -$N
Yes, this is one trivial case where definitely you would expect to
need an :i flag. The question is how you could generalize this well
enough to have something you can put into a lint program. Like I wrote
earlier, anything that does a head(1), tail(1), or sed -eq could at
least be candidates for adding an :i flag, but what would other
typical cases be?
/* era */
I can't help but think you'd need the lint program to be a sh lint
first and foremost if you want to be able to do anything at all at
this level. I'd worry more about typical newbie regex errors like a
lone trailing * and stuff like that.
--
Paparazzi of the Net: No matter what you do to protect your privacy,
they'll hunt you down and spam you. <http://www.iki.fi/~era/spam/>