Raul Thanks for finding that text-only item for me!
>"Linewrapping" is different from line breaking. Linewrapping is ok for English >it is designed for that, and we see it all the time. But line breaking where >extra linefeeds are actively inserted at what are essentially random places is >devastating for code, and not good for English ether. i am glad i at least >have found a workaround (that turns line breaking into linewrapping), and i >hope others will use that too - to make their posts more intelligible to me:) from: Raul Miller <[email protected]> to: Chat forum <[email protected]> date: 29 March 2013 13:14 subject: Re: [Jchat] [Jbeta] mailing browser On Fri, Mar 29, 2013 at 3:56 PM, greg heil <[email protected]> wrote: >>On a side note Google began pushing yesterday another revision of their gMail >>MUA. There are some benefits, but unfortunately it has a major killer (at >>least for me) in that it does not allow the creation of text-only posts. All >>posts must be in their rich-text format and suffer the overhead of being >>duplicated in a text only form. >For what it's worth, I have composed my response using gmail's new editor. >There's a menu on the lower right, that lets you toggle into "plain text >mode". You can also expand the quoted text so that it can be editted. >Linewrapping, I performed manually, in an external editor. Linewrapping is >painful for code, but nice for english. FYI, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
