Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Apr 1999 16:54:34 +0930
From:      Greg Lehey <>
To:        Nocturne <>
Cc:        Brad Benson <>, freebsd-chat@FreeBSD.ORG
Subject:   Re: outlook mail  was:(RE: Logo merchandise)
Message-ID:  <>
In-Reply-To: <>; from Nocturne on Thu, Apr 01, 1999 at 11:10:32PM -0800
References:  <000001be7b39$b40c2640$6400a8c0@BillyJoeBob> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thursday,  1 April 1999 at 23:10:32 -0800, Nocturne wrote:
> Greg Lehey wrote:
>> On Thursday,  1 April 1999 at 23:01:33 -0800, Nocturne wrote:
>>> Greg Lehey wrote:
>>> <snip>
>>>>>>>>>>>>>>>>>>>>>>>>> Sure, that works, but it's a workaround, and a barely acceptable one
>>>>>>>>>>>>>>>>>>>>>>>>> at that.  I've been corresponding with users of Microsoft platform
>>>>>>>>>>>>>>>>>>>>>>>>> mailers (there, Terry!), and they continually run into trouble because
>>>>>>>>>>>>>>>>>>>>>>>>> they're used to autowrap.
>>>> If you can reply to that without mutilating it, without entering
>>>> explicit CRs, and without making your own text too long, I'll be
>>>> impressed.  I think you *should* be allowed to reformat it, as long as
>>>> you keep the indentation level, something like this:
>>> Done.  As for explicit CRs, it's force of habit for me to hit return
>>> at the end of each line, it comes from my beginings of using pine
>>> which just scrolled over when your lines ran long.
>> Ah, but then you're working around the problem.  Most people who use
>> these mailers let the "editor" do the line wrap for them, but it's too
>> stupid to distinguish between what you enter and what was there
>> before.
> But the work around came from a problem with a very common unix-based
> mailer, not Netscape, so that makes it okay, right?  :-)

I don't understand.  Where's the problem with a UNIX-based mailer?

See complete headers for address, home page and phone numbers
finger for PGP public key

To Unsubscribe: send mail to
with "unsubscribe freebsd-chat" in the body of the message

Want to link to this message? Use this URL: <>