From: firewind <firewind AT metroid DOT dyn DOT ml DOT org>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: (none)
Date: 14 Oct 1997 18:41:04 GMT
Organization: Netcom
Lines: 31
Message-ID: <620ec0$rvs@sjx-ixn10.ix.netcom.com>
References: <Pine DOT SGI DOT 3 DOT 96 DOT 971013001807 DOT 3370A-100000 AT gibson DOT eee DOT upd DOT edu DOT ph>
NNTP-Posting-Host: elp-tx1-03.ix.netcom.com
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Orlando Andico <orly AT dilnet DOT upd DOT edu DOT ph> wrote:
> On 11 Oct 1997, Paul Derbyshire wrote:

> > Why the HELL did you UUENCODE a .c file? It's text..just post it plain so
> > we who have no binary-decoder crap can help you!

> It might have occurred to you that some mailers automagically encode all
> attachments (mine does -- PINE 3.96 for UNIX). 

I have PINE 3.95 running on Linux here, and .{c,h} files will be attached
as type text\plain... meaning, unencoded.

> Most of the Windows-based
> mailers encode attachments as MIME by default. So it might not be the
> previous poster's fault if he were unaware of this. 

It certainly is the poster's fault if he can't bother to RTFM.

> If you were unable to read his post, you were in no way obligated to
> answer it; but likewise, that didn't mean you had to yell at him. 

But for most people, reading these posts is too much trouble, so telling
the poster of the problem could help him get an answer to his question,
since nobody might bother too UUDECODE the message otherwise...

-- 
[- 				 firewind	                            -]
[-   email: firewind AT metroid DOT dyn DOT ml DOT org (home), firewind AT aurdev DOT com (work)  -]
[- 	    "You're just jealous because the voices talk to -me-."          -]
[-                   Have a good day, and enjoy your C.		            -]
[-          (on a crusade of grumpiness where grumpiness is due)            -]