Subject: .signature pipe

From: Jeff <[email-masked]>
Date: Fri, 13 Nov 1998 09:57:20 -0600 (CST)

Hello, all.

Have a curious situation:

I set up a perl program to feed a signature-like thing to a FIFO
named "~/.signature".  Works fine (`cat .signature` prints what I
want).  If I load up pine with the signature-file value as <Empty
Value> (not default), and then I ^R to read in .signature, it also
reads it in just fine.

But, if I set up pine with signature-file to be .signature, then
when I do a compose, it breaks the pipe.  I can only assume that the
way in which pine reads the signature file differs between a ^R read
and an automatic 'include signature on compose' read.

Anyone shed any light on this?

Thanks!
-jeff with a manually inserted .sig (not speaking for Learjet, I just
work there).

-----
Jeff Schaller                   [email-masked]
UNIX System Administrator       Phone:  (316) 946-7255
Learjet Inc                     Fax:    (316) 946-2809
 9:56am up 22:56, 8 users, load average: 0.09, 0.09, 0.09

-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Steve Hubert <[email-masked]>
Date: Sun, 15 Nov 1998 17:33:08 -0800 (PST)

Pine does a stat on the file to see how big it is and then reads that many
bytes, so that doesn't work right with named pipes. The next version of
pine will allow you to indicate that the sig file is a program instead of
a file to be read by appending a | character to that name.

-- 
Steve Hubert <[email-masked]>
Networks and Distributed Computing, Univ. of Washington, Seattle