Re: Quirks using format:fixed

2011-06-09 Thread Christian Brabandt
Hi Tim! On Mo, 06 Jun 2011, Tim Gray wrote: On Jun 06, 2011 at 05:20 PM +0200, Christian Brabandt wrote: I use a formatoption script, that uses a custom formatoption setting depending on the region the cursor is on. This allows to have different formatoptions for e.g. Header lines, quotes,

Re: Quirks using format:fixed

2011-06-06 Thread Christian Brabandt
Hi Tim! On Di, 17 Mai 2011, Tim Gray wrote: As far as wrapping my paragraphs in my message body, you need to have your vim options set correctly. I have the following set for when I edit mail in vim. You could get away with a subset of these. setlocal formatoptions=wtcqrn

Re: Quirks using format:fixed

2011-06-06 Thread Tim Gray
On Jun 06, 2011 at 05:20 PM +0200, Christian Brabandt wrote: I use a formatoption script, that uses a custom formatoption setting depending on the region the cursor is on. This allows to have different formatoptions for e.g. Header lines, quotes, code, etc.) Very cool. I'll have to digest

Re: Quirks using format:fixed

2011-05-18 Thread Richard
On Tue, May 17, 2011 at 12:25:35PM -0600, Aaron Toponce wrote: On Tue, May 17, 2011 at 03:30:13PM +0200, Richard wrote: the more practical idea is to edit plain text (or some kind of markup/richtext) in your favorite editor and have a wrapper script around the editor which converts

Re: Quirks using format:fixed

2011-05-17 Thread Richard
On Mon, May 16, 2011 at 09:59:19AM -0600, Aaron Toponce wrote: I don't mind tasteful, minimalistic HTML mail, but composing such in Vim is a major PITA. Plain text is so much easier to compose in that regard. I guess I could create macros, et cetera, et cetera, but it's still more work than

Re: Quirks using format:fixed

2011-05-17 Thread JP Bruns
Richard [17.Mai.2011 15:30]: On Mon, May 16, 2011 at 09:59:19AM -0600, Aaron Toponce wrote: I don't mind tasteful, minimalistic HTML mail, but composing such in Vim is a major PITA. Plain text is so much easier to compose in that regard. I guess I could create macros, et cetera, et cetera,

Re: Quirks using format:fixed

2011-05-17 Thread Tim Gray
On May 17, 2011 at 12:25 PM -0600, Aaron Toponce wrote: Or, I could just set tw=0 for vim, and enable format:flowed in my ~/.muttrc. That would probably be the easiest route. It's unclear from your message whether or not you realize this, but setting f=f in your muttrc doesn't actually do

Re: Quirks using format:fixed

2011-05-17 Thread Tim Gray
On May 12, 2011 at 02:28 PM -0600, Aaron Toponce wrote: Is there are way to tell Vim not to wrap the headers, even though I wish to wrap the body? I hardly ever edit the headers in my editor, vim or otherwise. I do that all from the mutt interface. I have Vim (and my other editor) set up

Re: Quirks using format:fixed

2011-05-17 Thread Ed Blackman
On Tue, May 17, 2011 at 02:42:03PM -0400, Tim Gray wrote: On May 17, 2011 at 12:25 PM -0600, Aaron Toponce wrote: Or, I could just set tw=0 for vim, and enable format:flowed in my ~/.muttrc. That would probably be the easiest route. It's unclear from your message whether or not you realize

Re: Quirks using format:fixed

2011-05-16 Thread Richard
On Sun, May 15, 2011 at 11:57:19AM -0400, Tim Gray wrote: On May 15, 2011 at 02:51 PM +0200, Richard wrote: I was wondering if anyone has a script to convert normal mail messages to format flowed stuff and back? Could be used as an editor wrapper script instead of trying to reimplement the

Re: Quirks using format:fixed

2011-05-15 Thread Richard
On Thu, May 12, 2011 at 02:28:31PM -0600, Aaron Toponce wrote: Further, wrapping your mail at a predetermined width seems to have problems with users on smaller screens, such as mobile devices. So, I'm wondering if using format:fixed is appropriate, or if I should be using format:flowed? If I

Re: Quirks using format:fixed

2011-05-15 Thread Tim Gray
On May 15, 2011 at 02:51 PM +0200, Richard wrote: I was wondering if anyone has a script to convert normal mail messages to format flowed stuff and back? Could be used as an editor wrapper script instead of trying to reimplement the functionality in every editor. I did something like this a