Re: Sorry had to post this
On Tue, Jun 19, 2001 at 11:18:22PM +0530, Angshuman Dasgupta wrote: The problem is not with my mailer but with the original poster's mailer. My mailer is mutt + vi which doesn't insert stupid newlines into a line to break it up. If your mailer doesn't break lines up, then you do have a problem. It is bad email form to keep messages as one big line. The problem is that recipients, with clients like mutt or pine, will insert a break at the character that touches the end of the line, rather than go about it intelligently. Then you might wind up with lines that look like such: My mailler is mutt + vi whic +h doesn't insert newlines i +nto a line to break it up. It is th sender who is responsible for breaking messages into an orderly block of text, not the recipient. And newlines used for this purpose aren't stupid, they are necessary to preserve the sanity of email, and its readers' good moods. As you will see above, mutt also chokes on your unbroken line, because it puts a reply arrow at the beginning of the line only. If you have color enabled, you will see the first line of your reply text is green, but the second is not. Certainly it is easy to make out what is what, but this is not the case in long messages. It makes for rough reading. If you use vim with mutt, you can set the vim arguments to be + -c set textwidth=72 -c set wrap and it will wrap characters with the generally accepted standard 72-column width. This will help maintain your good reputation on mailing lists like this. There are many (myself included) who simply ignore unwrapped messages, because reply text becomes a nightmare. Yours is the only exception I've made in a number of months. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Sorry had to post this
Exactly how many people need to verify that the link isn't broke in order for you to believe that it's working? Take a vacation... -- scott On Tue, 19 Jun 2001, Scott Reese wrote: The link IS broken. Even if you paste the entire URL into the browser, it still says the page is unavailable. -Scott [EMAIL PROTECTED] wrote: The link isn't broken, the line is... Chris On Tue, Jun 19, 2001 at 09:14:22AM -0400, Ken Menzel wrote: In short, this is a URL to an article describing Microsoft's current and past use of FreeBSD dated June 18th, 2001 http://interactive.wsj.com/fr/emailthis/retrieve.cgi?id=SB992819157437 237260.djm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: Sorry had to post this
The problem is not with my mailer but with the original poster's mailer. My mailer is mutt + vi which doesn't insert stupid newlines into a line to break it up. Then your mailer isn't RFC-compliant... From 2822: There are two limits that this standard places on the number of characters in a line. Each line of characters MUST be no more than 998 characters, and SHOULD be no more than 78 characters, excluding the CRLF. Yes, that's a SHOULD instead of a MUST for 78 characters, but ignoring SHOULD's is still a bad thing. ...arun To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Sorry had to post this
If you use vim with mutt, you can set the vim arguments to be + -c set textwidth=72 -c set wrap and it will wrap characters with the generally accepted standard 72-column width. And, since this is a FreeBSD mailing list, and he =said= he used vi: set wraplen=68 for the same effect. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
