Re: ispell with vim
On 16.05.11 16:55, Robert Holtzman wrote: Unfortunately my (Ubuntu's) version of Mutt seems to have been compiled without ispell capability. From mutt -v: -ISPELL. Not having enough background in compiling programs, I'll just stick to this in vimrc. map F6 Esc:setlocal spell spelllang=en_usCR map F7 Esc:setlocal nospellCR That's all I use (except it's ^E for English, and ^D for Danish), and it seems ideal to me. I'm a bit puzzled about how mutt could be expected to come into the spelling picture? Erik -- The surest way to corrupt a youth is to instruct him to hold in higher regard those who think alike than those who think differently. - Nietzsche
Re: Quirks using format:fixed
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 just composing plain text, and letting the lien wrap automatically. 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 that to/from html. I have done that once and it worked pretty well back then but did not have the need for it since a few years. If you are interested I could revive the script and dig out the details of the configuration that I used. Back then the configuration was a bit tricky and it did not play well with attachments. Richard --- Name and OpenPGP keys available from pgp key servers pgpxGKSRe21PR.pgp Description: PGP signature
Can't figure out how to set locale/charset stuff
It's been years since mutt displayed more than a small fraction of my incoming mail correctly. I've tried setting LC_CTYPE and LANG according to http://wiki.mutt.org/?MuttFaq/Charset, but no matter what I choose, there's always a large percentage of mails that won't display properly. Some of my e-mail comes in as UTF-8, some as IS0-8859-1, so I don't see how picking one or the other is ever going to work right. Is there any other documentation on how to get mutt to display a variety of encodings/charsets? -- Grant Edwards grant.b.edwardsYow! Am I in Milwaukee? at gmail.com
Re: Can't figure out how to set locale/charset stuff
On 2011-05-17, Grant Edwards grant.b.edwa...@gmail.com wrote: It's been years since mutt displayed more than a small fraction of my incoming mail correctly. I've tried setting LC_CTYPE and LANG according to http://wiki.mutt.org/?MuttFaq/Charset, but no matter what I choose, there's always a large percentage of mails that won't display properly. For example, When I look at an e-mail like this: --B_3388474568_4536735 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable delimiter (e.g. =8C.=B9) I see this: delimiter (e.g. \214.¹) [the character before the ')' is a superscript 1. I presume it's supposed to be some sort of close-quote.] I'm using urxvt as my terminal, and the touch/ls test with a non-ascii filename suggested by http://wiki.mutt.org/?MuttFaq/Charset works fine. -- Grant Edwards grant.b.edwardsYow! Psychoanalysis?? at I thought this was a nude gmail.comrap session!!!
Re: Quirks using format:fixed
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, but it's still more work than just composing plain text, and letting the lien wrap automatically. 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 that to/from html. I have done that once and it worked pretty well back then but did not have the need for it since a few years. If you are interested I could revive the script and dig out the details of the configuration that I used. Back then the configuration was a bit tricky and it did not play well with attachments. Which reminds me: would txt2tags [1] be of any help? You could at least use some simple tags and convert that to html (among others). I don't know how well it integrates with mutt. Jens [1] http://txt2tags.org/
Re: Quirks using format:fixed
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 diddly-squat to the actual formatting of your message. It just sets a header to let recipients know that the message body is expected to be f=f. I think it also does another step (space stuffing), but it does NOT add the proper trailing spaces to paragraphs which should be wrapped. That needs to occur in the editor or in a wrapping script. I hope I have the above correct. For what it's worth, I have no problems with my format=flowed email in any of the mail clients I've used, including on my iPhone - it wraps it just like it should even though it displays only something like 55 characters per line. I haven't tried any ancient mail clients, but I would suspect they'd be ok with mail that is hard wrapped at 72 characters anyway. pgpsWYQ3Z9ZXa.pgp Description: PGP signature
Re: Can't figure out how to set locale/charset stuff
Grant Edwards schrieb am 17.05.2011 um 16:40 (+): On 2011-05-17, Grant Edwards grant.b.edwa...@gmail.com wrote: It's been years since mutt displayed more than a small fraction of my incoming mail correctly. I've tried setting LC_CTYPE and LANG according to http://wiki.mutt.org/?MuttFaq/Charset, but no matter what I choose, there's always a large percentage of mails that won't display properly. Here are my settings: # set locale= de_DE@euro# aus Umgebung set charset = utf-8 set send_charset= us-ascii:iso-8859-1:utf-8 charset-hook us-ascii iso-8859-1 charset-hook ^unknown-8bit$ windows-1252 charset-hook ^x-user-defined$ windows-1252 charset-hook ^iso-8859-1$ windows-1252 charset-hook ^us-ascii$ windows-1252 The locale doesn't appear to work on Cygwin, but never mind. http://wiki.mutt.org/?MuttFaq/Charset delimiter (e.g. =8C.=B9) I see this: delimiter (e.g. \214.¹) I'm using urxvt as my terminal, and the touch/ls test with a non-ascii filename suggested by http://wiki.mutt.org/?MuttFaq/Charset works fine. I'm using MinTTY, which is just great. And my Mutt is linked against ncursesw, Although mutt -v will claim mutt is compiled with just ncurses (which might be true, after all), ldd reveals the true linkage occurring: cygncursesw-10.dll = /usr/bin/cygncursesw-10.dll (0x6ed1) Read this thread: http://cygwin.com/ml/cygwin/2010-06/msg00173.html Andy Koppe, the MinTTY developer, said this: […] vim works fine with UTF-8 already. […] Mutt and also nano do need rebuilding with ncursesw though. -- Michael Ludwig
Re: Quirks using format:fixed
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 to not mess with lines I don't edit. So they don't munge headers. 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 setlocal tw=72 setlocal noai setlocal nosi I set text wrapping to 72 columns (tw). I turn off auto indenting (noai) and smart indenting (nosi). The format options are explained in vim's help under 'fo-table'. But the short story on them is the following: - t - autowrap text using textwidth - c - autowrap comments using textwidth - add comment leader - q - allow formatting comments with 'gq' command - r - auto insert comment leader after hitting enter in insert mode while in a comment - n - recognize numbered lists while formating - w - trailing white space indicates a paragraph continues to the next line. a line that ends in a non-white character ends the paragraph. The 'w' option is the pertinent one if you set format=flowed. The way the above settings works is that as I type long wrapped paragraphs, vim automatically adds line breaks and a trailing space on those lines (satisfying the requirements of f=f). Lines that I don't edit don't get line breaks added. If I edit a wrapped paragraph, I usually have to manually run 'gq' on that paragraph to get it formatted correctly - if you don't want to have to do that, you can look into adding the 'a' option to the formatoptions. You also might be interested in the 'v', 'b', and'l' options, which control how vim wraps lines depending on their lengths, content, and how you edit the line. For example, I should enable the 'l' option... Hope this helps. And if you already knew this stuff, please disregard. pgpEZyLC5cxRc.pgp Description: PGP signature
Re: Quirks using format:fixed
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 this, but setting f=f in your muttrc doesn't actually do diddly-squat to the actual formatting of your message. It just sets a header to let recipients know that the message body is expected to be f=f. I think it also does another step (space stuffing), but it does NOT add the proper trailing spaces to paragraphs which should be wrapped. That needs to occur in the editor or in a wrapping script. I hope I have the above correct. That's correct from my experience. You need to set the header in mutt, AND make sure that the message is formatted as specified in the format=flowed RFC 3676 (short summary, a trailing space at the end of lines that you want to flow). That's because you're allowed to have fixed lines inside a format=flowed message. I got tired of checking whether a given line ended with a space (which was chosen precisely because its prescence at the end of lines wouldn't be very noticible in clients that didn't support RFC 3676), and created a vim mail syntax plugin that puts a white underscore at the end of lines that end with a space, so I can see at a glance which lines will flow and which won't. -- Ed Blackman signature.txt Description: Digital signature
Re: priority of send-hooks and folder-hooks
On Mon, May 16, 2011 at 09:53:34AM +0200, Thorsten Scherf wrote: I did some signature configuration based on folder-hooks and send-hooks. As default send-hook, I've choosen a specific signature that changes based on different recipient addresses. I now want to change the signature also based on specific holders, but it looks like the config I did for send-hooks has preference over the folder-hook config. Is there any way to change this behaviour? Can you elaborate more specifically on what you want to accomplish? It's unclear to me if you are attemping to set a specific signature per folder that overrides your default recipient send-hooks.
