🚀 go-pugleaf

Matthias Urlichs writes:

> End of file. You'd have to wait for both tail processes to finish before you
> could start the diff

How come?  Can't I start as soon as there's something there, even in the
case of a file?

> You could probably create the temp files, mandatory-lock them, and then 
> exec the tail processes. If the diff waits for the lock correctly (that's why
> the lock has to be mandatory) you have a workable lockout.

Ah, I see -- you have to be able to know when the file is all done with.

> Or their .signature. ;-)

Moi? :-)

> Ugh. I'd include almost every development tool. Or take cp for instance --
> do you still want to be able to copy executable files?  ;-)

Yes, I'm not happy with it happening ALWAYS.  I think either a mode on 
the file (or type) or else an explicit open that way "[rw]x" would be 
better.

> If you happen to be one of the fretful minority who can do creative work,
> never force an idea; you'll abort it if you do. Be patient and you'll give
> birth to it when the time is ripe. Learn to wait.
>                 -- Lazarus Long

ah thanks; (cat; echo %%) >> ~/News/SIGNATURES

--tom

-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist

    "* Unix is a footnote of AT&T Bell Laboratories."
                             --Barry Shein