Date: Fri, 2 Apr 1999 16:37:27 +0930 From: Greg Lehey <grog@lemis.com> To: Nocturne <dpilgrim@uswest.net> Cc: Brad Benson <bradley@softhome.net>, freebsd-chat@FreeBSD.ORG Subject: Re: outlook mail was:(RE: Logo merchandise) Message-ID: <19990402163727.C413@lemis.com> In-Reply-To: <37046B4D.47BC1A7E@uswest.net>; from Nocturne on Thu, Apr 01, 1999 at 11:01:33PM -0800 References: <000001be7b39$b40c2640$6400a8c0@BillyJoeBob> <370465AC.95322011@uswest.net> <19990402162222.A413@lemis.com> <37046B4D.47BC1A7E@uswest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990402163727.C413>