Re: allow_ansi set, but I only get the first character highlighted
On Thu, Apr 12, 2012 at 09:58:40PM +0200, Michael Ludwig wrote: > lilydjwg schrieb am 11.04.2012 um 19:40 (+0800): > > I'm using elinks to view those HTML emails. ~/.mailcap contains: > > > > text/html; muttHtml; copiousoutput > > Not answering your questions, but as you appear to like Python: > > https://bitbucket.org/blacktrash/muttils > > This allows you to have FF or IE or display your mail. Thanks, these tools are useful for me. -- Best regards, lilydjwg Linux Vim Python 我的博客: http://lilydjwg.is-programmer.com/ -- A: Because it obfuscates the reading. Q: Why is top posting so bad?
Re: Hide [bracketed topic indicators] such as prepended by mailing lists
* On 12 Apr 2012, Michael Ludwig wrote: > > Applied against current trunk from Mercurial, together with trash folder > patch; some fuzz, but no conflicts. Works as advertised, see above. > The configuration is straightforward if you know regular expressions: > > subjectrx '\[Firebird-net-provider\] *' '%L%R' > subjectrx '\[FB-Tracker\] Created: *' '%L%R' > > Thanks, David! Glad it helps. It may not have been clear in my post, or maybe this isn't really what you want, but this config: subjectrx '^(re: *)?\[[^]:]*\] *' '%1%R' should perform the replacement for *any* list tag that appears at the beginning or after a re: prefix. (I find ones appearing later in the subject useful, since the usually indicate that the message came from another list that I'm not subscribed to.) Note that this does not hide [tags] with colons in them -- those are usually some other kind of markup that may be meaningful. -- David Champion • d...@uchicago.edu • IT Services • University of Chicago
Re: Hide [bracketed topic indicators] such as prepended by mailing lists
David Champion schrieb am 13.04.2012 um 11:37 (-0500): > […] this config: > > subjectrx '^(re: *)?\[[^]:]*\] *' '%1%R' > > should perform the replacement for *any* list tag that appears at the > beginning or after a re: prefix. Great - I find this setting more convenient than having to specify a dozen separate tags. Thank you! Michael
Seeding and updating mutt's header and body caches
Hey, I've noticed that mutt only caches message headers and bodies after it has had to download the header/body once before. For example, the first time you open a large imap folder it'll take a long time while mutt downloads all of the headers. The next times it will be faster. The first time you search the bodies of emails in a large imap folder it'll take an extremely long time as mutt downloads the bodies (including attachments) of all messages in the folder. The next times it will be much faster. So if you open every imap folder in your imap account and search for `~b foobar` then things will be much faster for you later, when you're trying to open and search folders because you actually need something. But you'd have to repeat this manual process periodically as new, not-yet-cached mails are added to the folders. I wonder if it's possible to write a script that would get mutt to open every folder in an imap account and download all of the message bodies and headers into its cache? You could run it from cron to keep your mutt working reasonably fast.
Strange characters in Re: subject lines
Hi, I just compiled Mutt 1.5.21 on Linux Mint Debian, using service pack 4. Mutt seems to be running fine except for one thing - when I sort my messages by subject, every subsequent subject line under the original post in a thread shows strange characters like "M-b~T~B M-b~T~TM-b~T~@>", with no other meaningful characters in the line. I also see similar characters in subject lines that have apostrophes. I'm using Xfce terminal emulator 0.4.8. (xterm fares no better). I've checked the xfce terminal preferences, and bold text is enabled. If it's some sort of language encoding issue, I might need some pointers how to change those settings. -- Eric Patton
Re: Seeding and updating mutt's header and body caches
> [...] The first time you search the bodies of emails in a large imap > folder it'll take an extremely long time as mutt downloads the bodies > (including attachments) of all messages in the folder. The next times > it will be much faster. [...] Depends on your IMAP server; some can handle search *server-side*, which gets rid of the need to “mirror” the message bodies locally. Unfortunately, IMAP search only works with substrings, hence won't handle regular expressions; nonetheless, search with “=b” instead of “~b” and mutt will automagically switch to server-side search if possible. As for your original question, I believe a simpler way to help with IMAP search speed would involve offlineimap (or similar) that'd mirror your server locally. Mutt would still need to cache the message bodies but at least they'd already be stored on your machine, avoiding the server round-trips involved in a search on a “yet unsearched” folder. -- --|-- | Patrice Levesque http://ptaff.ca/ mutt.wa...@ptaff.ca | --|-- -- signature.asc Description: Digital signature
