Re: big mailbox v.s. rotated mailbox; thoughts
msg.pgp Description: PGP message
Re: Moving between folders
I'm glad to read good tricks about mutt. The document (manual.txt) is too short of examples that we have to pull out handfuls of hairs to get a function work. :) charlie -- On Thu, Dec 27, 2001 at 02:39:48AM -0700, Rob 'Feztaa' Park wrote: On Thu, Dec 27, 2001 at 01:36:51PM +0800, Charles Jie (dis)graced my inbox with: You should not keep that many messages in a working 'folder' (indeed file). You'd better initialize a new one for high traffic folder yearly, quarterly or even monthly. I agree, I automatically move all my old mail into compressed folders that are named for the year and month of the mails in them. If you need help setting that up, just ask :)
Re: big mailbox v.s. rotated mailbox; thoughts
On Thu, Dec 27, 2001 at 09:41:11PM +0100, Michael Wagner [EMAIL PROTECTED] wrote: On Donnerstag, 27. Dez. 2001 at 18:33:53, Thomas Hurst wrote: I have a script scan all my mailspools (I use mbox) and move anything older than a week to archive/year/mailbox/month-year-mailbox - this keeps my active mail easily to hand, and searching for older mail's as easy as I need it to be. I have for this a folder-hook. It looks like this: folder-hook =mutt-users$ 'push T~r2w!~F\n\;s' I have a similar folder-hook: folder-hook =(ntbugtraq|bugtraq|fbsd-de-questions|fbsd-security|fbsd-chat|fbsd-arch|fbsd-hackers|fbsd-stable|mutt(-devel)?|gnupg)$ push \tag-pattern~d2w\nuntag-pattern~F|~D|~O|~N\ntag-prefix-condsave-message\n\nsync-mailboxfirst-entrynext-newredraw-screen\ And also I have a save-hook for this: save-hook ~L mutt-users =Archiv/mutt-users-archiv I set the save-hooks in many folder-hooks. But the effect is similar. The only thing, which does not work correct, is, then I enter the folder mutt-users and there is no message which is older than 2 weeks, mutt always wants to save the message on which the cursor stays. How can I change my folder-hook, that mutt don't show such a behaviour. I have written a small patch to address this problem, look for tag-prefix-cond in the folder-hook. You can find the patch on my homepage (www.rachinsky.de). It is tested with FreeBSD Port of 1.3.23.2. PS: Some time ago I also worked with a script which invoked grepmail, but now I think, it's better to make it with mutt. I want to use a small script to move very old mails to compressed folders, it should work, but it is still untested. I attach it. Nicolas move_mail.sh Description: Bourne shell script
charset in text/plain attachments: how to tune?
mutt-1.2.5i i have charset=koi8-r in .muttrc, but mutt always assumes that my text/plain attachments are in us-ascii charset if there is no certain charset record in `Content-Type:' field. so i need to edit-type or manually recode affected attachments :-(. mutt-1.0i works more suitable ;-) using charset from user locale (or may be $MM_CHARSET) while display attachments _without_ charset specified in `Content-Type:' field. do you know how to avoid such a behaviour of 1.2.5? 10x in advance, ~borman
Re: ~A and the definition of all
Maciej Kalisiak muttered: For some of us mutt's current behaviour in this regard is non-intuitive, so clearing these things up in the manual would help us from pulling our hair out. I got bitten badly by the ambiguity in the manual regarding the ~A pattern. Naive me thought that all messages means all messages, and would have never guessed it meant all *visible* messages. I don't find it uninuitive, BUT you're right the manual is unclear in some respect. Imagine you (l)imit a certain pattern and want to move those messages to another place. Tag all, tag-save, done. Easy and the behavior _I_ would expect. I rarely use collapsing; though. My default folder view is with collapsed threads and I was opening mh folders and moving all messages to new mbox style ones: T~A\n;s=newmbox\n After checking that the first few mailboxes were transferred correctly (which as fate would have it didn't have more than one message per thread) I did the rest quickly. As deleted messages in mh folders still leave files, I rm -rf those directories once they were converted. Only three-quarters of the way through did I realize that the collapsed messages were not being copied over. Argh!!! Luckily I can probably get 95% of the lost messages from various backups, but it's a massive headache. Poor guy!!! After browsing the Net on this topic I later found that apparently other commands also ignore collapsed messages (I think searching was one of them). Can someone list which commands ignore threads and which don't? search and tag ignore messages in collapsed threads limit doen't. Any more? HTH, Michael -- PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: charset in text/plain attachments: how to tune?
boris karlov muttered: i have charset=koi8-r but mutt always assumes that my text/plain attachments are in us-ascii charset if there is no certain charset record in `Content-Type:' field. do you know how to avoid such a behaviour of 1.2.5? Look for charset-hook in the manual. HTH, Michael -- Are [Linux users] lemmings collectively jumping off of the cliff of reliable, well-engineered commercial software? (By Matt Welsh) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: charset in text/plain attachments: how to tune?
On Fri, Dec 28, 2001 at 03:04:41PM +0100, Michael Tatge wrote: boris karlov muttered: i have charset=koi8-r but mutt always assumes that my text/plain attachments are in us-ascii charset if there is no certain charset record in `Content-Type:' field. do you know how to avoid such a behaviour of 1.2.5? Look for charset-hook in the manual. -- in muttrc(5) i've seen: charset-hook alias charset This command defines an alias for a character set. This is useful to properly display messages which are tagged with a character set name not known to mutt. ...messages which _are_tagged_ with a character set name not to mutt... but i mean attachments with Content-Type: text/plain, there is no charset part _at_all_. 10x in advance, ~borman
Re: charset in text/plain attachments: how to tune?
boris karlov muttered: On Fri, Dec 28, 2001 at 03:04:41PM +0100, Michael Tatge wrote: boris karlov muttered: i have charset=koi8-r but mutt always assumes that my text/plain attachments are in us-ascii charset if there is no certain charset record in `Content-Type:' field. do you know how to avoid such a behaviour of 1.2.5? Look for charset-hook in the manual. charset-hook alias charset This command defines an alias for a character set. This is useful to properly display messages which are tagged with a character set name not known to mutt. ...messages which _are_tagged_ with a character set name not to mutt... but i mean attachments with Content-Type: text/plain, there is no charset part _at_all_. Well, is a charset too, isn't it? charset kio8-r or the matching ISO-whatever does what you want. I use charset-hook iso-8859-1 for the very same reason. Mutt assumes us-ascii, if nothing is specified - according to the relevant RFCs, I presume. I often get mail with German umlauts from people with broken mailers and the above helps me reading those messages a lot. :) HTH, Michael -- Avoid the Gates of Hell. Use Linux (Unknown source) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: charset in text/plain attachments: how to tune?
On Fri, Dec 28, 2001 at 03:56:56PM +0100, Michael Tatge wrote: boris karlov muttered: On Fri, Dec 28, 2001 at 03:04:41PM +0100, Michael Tatge wrote: boris karlov muttered: i have charset=koi8-r but mutt always assumes that my text/plain attachments are in us-ascii charset if there is no certain charset record in `Content-Type:' field. do you know how to avoid such a behaviour of 1.2.5? Look for charset-hook in the manual. charset-hook alias charset This command defines an alias for a character set. This is useful to properly display messages which are tagged with a character set name not known to mutt. ...messages which _are_tagged_ with a character set name not to mutt... but i mean attachments with Content-Type: text/plain, there is no charset part _at_all_. Well, is a charset too, isn't it? -- i've tried this already. but, unfortunately, it does not work: :charset-hook koi8-r\n empty (sub)expression gonna try `charset-hook another_regexp koi8-r' (e.g. `charset-hook .* koi8-r' ;-)) Michael, 10x. charset kio8-r or the matching ISO-whatever does what you want. I use charset-hook iso-8859-1 for the very same reason. Mutt assumes us-ascii, if nothing is specified - according to the relevant RFCs, I presume. I often get mail with German umlauts from people with broken mailers and the above helps me reading those messages a lot. :)
Using message-hook to run messages through a filter
There is one guy out there who has particular and very annoying writing idiosyncracies (think Prince or B1FF). I wrote a filter to translate his prose to something less obnoxious. Now how do I configure Mutt to automatically pipe his messages through the filter when reading or replying to him ? I thought that message-hook ~f joe@blow\.com pipe-message /usr/local/bin/unmangle would do the trick but Mutt says pipe-message: unknown command. -- André Majorel URL:http://www.teaser.fr/~amajorel/ std::disclaimer (Not speaking for my employer);
Re: Using message-hook to run messages through a filter
On Fri, Dec 28, 2001 at 05:09:05PM +0100, Andre Majorel [EMAIL PROTECTED] wrote: I thought that message-hook ~f joe@blow\.com pipe-message /usr/local/bin/unmangle would do the trick but Mutt says pipe-message: unknown command. I would try message-hook . unset display_filter message-hook ~f joe@blow\.com set display_filter=/usr/local/bin/unmangle but this is untested. Nicolas
Re: Using message-hook to run messages through a filter
On Fri, Dec 28, 2001 at 05:09:05PM +0100, Andre Majorel wrote: There is one guy out there who has particular and very annoying writing idiosyncracies (think Prince or B1FF). I wrote a filter to translate his prose to something less obnoxious. Now how do I configure Mutt to automatically pipe his messages through the filter when reading or replying to him ? I thought that message-hook ~f joe@blow\.com pipe-message /usr/local/bin/unmangle would do the trick but Mutt says pipe-message: unknown command. well, not sure how to do it with mutt - I have written a similar filter (for a 40 year old that spells like he's a teenage hacker wannabe), and I just run it via procmail... It is funny to see my replies to him spelled correctly (including the quoted part :) HTH Dan -- Dan Boger [EMAIL PROTECTED] msg21980/pgp0.pgp Description: PGP signature
problem with timestamps
Hi, I hope I can make this clear, when mutt modifies a file (mbox) it doesn't update the timestamps. Mutt 1.3.24i (2001-11-29) Any idea?
Re: new subject line format/threading
also sprach David Clarke [EMAIL PROTECTED] [2001.12.28.0413 +0100]: I'd grab the deb source and the patch and see if it applys, if it does you can just build your own mutt deb with dpkg-buildpackage. sure, i know *how* to do it, but it's too much trouble. i just don't want to deal with it. it's okay for me to wait, it's just a cosmetic thing anyway... thanks though. -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; net@madduck i'd give my right arm to be ambidextrous. msg21982/pgp0.pgp Description: PGP signature
Mutt and Tiff's
Hello, I receive faxes in my mail these days but I cannot find anywhere (and I have looked) for a viewer I could use in Mutt to read them since they come in as tiff files. Any pointers --- -- Regards Cliff
Re: charset in text/plain attachments: how to tune?
boris karlov muttered: On Fri, Dec 28, 2001 at 03:56:56PM +0100, Michael Tatge wrote: Well, is a charset too, isn't it? i've tried this already. but, unfortunately, it does not work: :charset-hook koi8-r\n empty (sub)expression Strange canÄt reproduce this with 1.2.5: $ ./mutt -v Mutt 1.2.5i (2000-07-28) mutt -F /dev/null :charset-hook koi8-r no error message. Since I do not have a kyrillic charset installed I get ? as expected. Michael -- All language designers are arrogant. Goes with the territory... (By Larry Wall) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: Using message-hook to run messages through a filter
Date: Fri, 28 Dec 2001 17:09:05 +0100 From: Andre Majorel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Using message-hook to run messages through a filter There is one guy out there who has particular and very annoying writing idiosyncracies (think Prince or B1FF). I wrote a filter to translate his prose to something less obnoxious. Now how do I configure Mutt to automatically pipe his messages through the filter when reading or replying to him ? I thought that message-hook ~f joe@blow\.com pipe-message /usr/local/bin/unmangle would do the trick but Mutt says pipe-message: unknown command. It's pipe-message (incl. the angle brackets) isn't it? -- FreeBSD 4.4-STABLE 6:21PM up 2 days, 4:59, 11 users, load averages: 0.00, 0.01, 0.00
Case sensitivity in regular expressions
Although the manual doesn't explicitly mention it, regular expressions in mutt seem to be case insensitive. So even although mutt supports [:lower:] and [:upper:], they do not work as expected and end up being equivalent to [:alpha:]. So does anyone know solutions to this, overrides in mutt, or any helpful patches. -- Benjamin Smith [EMAIL PROTECTED], [EMAIL PROTECTED] msg21986/pgp0.pgp Description: PGP signature
Re: Case sensitivity in regular expressions
On Fri, Dec 28, 2001 at 05:17:27PM +, Benjamin Smith wrote: Although the manual doesn't explicitly mention it, regular expressions in mutt seem to be case insensitive. So even although mutt supports [:lower:] and [:upper:], they do not work as expected and end up being equivalent to [:alpha:]. So does anyone know solutions to this, overrides in mutt, or any helpful patches. From the mutt manual: 4.1. Regular Expressions ... The search is case sensitive if the pattern contains at least one upper case letter, and case insensitive otherwise. So it may be that the pattern must contain at least one literal upper-case letter to be case-sensitive and that [:upper:] doesn't count for that. If using [:upper:] doesn't make the search case-sensitive, I would say that's a bug. HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: Case sensitivity in regular expressions
On Fri, Dec 28, 2001 at 12:40:26PM -0800, Gary Johnson wrote: On Fri, Dec 28, 2001 at 05:17:27PM +, Benjamin Smith wrote: Although the manual doesn't explicitly mention it, regular expressions in mutt seem to be case insensitive. So even although mutt supports [:lower:] and [:upper:], they do not work as expected and end up being equivalent to [:alpha:]. So does anyone know solutions to this, overrides in mutt, or any helpful patches. From the mutt manual: 4.1. Regular Expressions ... The search is case sensitive if the pattern contains at least one upper case letter, and case insensitive otherwise. So it may be that the pattern must contain at least one literal upper-case letter to be case-sensitive and that [:upper:] doesn't count for that. If using [:upper:] doesn't make the search case-sensitive, I would say that's a bug. I must have missed that when I read that section. Thanks. Before I tried [:upper:] I tried [A-Z] and it didn't seem to work either (I was doing '~s [A-Z]' and it still showed messages *not* containing any upper case letters). Perhaps 'bracketed' things somehow miss the check for upper case letters. It probably doesn't check everything for upper case letters as (presumably) something like ~C shouldn't get taken as one. I had a quick glance at the source, but state machines and re compilers are not really *that* fun. HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ | -- Benjamin Smith [EMAIL PROTECTED], [EMAIL PROTECTED] msg21988/pgp0.pgp Description: PGP signature
Possible to add a user-defined field Keyword to read message before/when save?
Obviously I don't mean 'e' (edit) command count. The purpose of it is that I want to give keywords or category to read messages so that I can search them easier later. If I can add this field easily when I save it or before I press 's' with ease, I don't bother to save messages into that many folders. :) charlie
Re: Possible to add a user-defined field Keyword to read message before/when save?
On Sat, Dec 29, 2001 at 11:17:51AM +0800, Charles Jie (dis)graced my inbox with: Obviously I don't mean 'e' (edit) command count. The purpose of it is that I want to give keywords or category to read messages so that I can search them easier later. If I can add this field easily when I save it or before I press 's' with ease, I don't bother to save messages into that many folders. :) I'm not entirely sure what you are asking, but it seems as though you just want to save messages into different folders. That way they'll be organized into different categories for easier searching... -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- Once you've put one of his books down, you simply can't pick it up again. -- Mark Twain (talking about Henry James) msg21990/pgp0.pgp Description: PGP signature
Re: Possible to add a user-defined field Keyword to read message before/when save?
Thus spake Charles Jie ([EMAIL PROTECTED]): Obviously I don't mean 'e' (edit) command count. The purpose of it is that I want to give keywords or category to read messages so that I can search them easier later. If I can add this field easily when I save it or before I press 's' with ease, I don't bother to save messages into that many folders. :) I think something that might accomplish this would be to add an X-header to the message after reading, similar to the way that Evolution adds a custom header (for some purpose or another). Aside from editing the message, perhaps passing it to a shell command that would take a keyword or such and add the header? Anyone see what I'm talking about? Perhaps someone can build on the idea... -- Justin R. Miller [EMAIL PROTECTED] View my website at http://codesorcery.net Please encrypt email using key 0xC9C40C31 msg21991/pgp0.pgp Description: PGP signature
Re: Configuration problems
On Thu, Dec 27, 2001 at 02:17:53PM +0100, René Clerc wrote: And, since you're signing your list email, please upload your public key to the keyservers. So did I. Err... I did, didn't I? ;) Yeah, you did ;-) -- David Rock [EMAIL PROTECTED] msg21992/pgp0.pgp Description: PGP signature
