[Elecraft] Avoiding those long lines of text we struggle to read!

Leo Bricker K5LDB k5ldb.leo at gmail.com
Wed Dec 26 10:03:30 EST 2007


>> It is still considered good practice for email clients to wrap text in
>> outgoing email to less than 80 characters.
>>     
>
>   That makes it break the common long URIs for a particular
> product or article.  It also wraps a reply, causing alternate
> long lines with a word or two on the next line when the original
> has been formatted correctly with linefeeds embedded.
>   I haven't read RFC2822 in over six years at least: I'm
> pretty sure it doesn't recommend setting automatic line wrap on
> an editor, at least for the reasons I mentioned above. I remember
> that it sets a limit on how long a line should be - under manual
> control using the "return" key every so often.
>
> Ian, G4ICV, AB2GR, K2 #4962
>   
Unless one is typing on a manual typewriter or has reached the end of a 
paragraph and is hitting return to add a blank line before the next 
paragraph then one shouldn't put a linefeed in their message in my 
opinion. Also, anyone posting a URL in a message should go to 
www.tinyurl.com and convert it before inputting it. There's no excuse to 
have a long URL in a message anymore.

-- 
73 K5LDB
----------
Support the entire Constitution, not just the parts you like.



More information about the Elecraft mailing list