* mutt-users-digest <[EMAIL PROTECTED]> [020102 16:19]: > > mutt-users-digest Saturday, December 29 2001 Volume 01 : Number 909 > > > > Today's Topics: > > Re: big mailbox v.s. rotated mailbox; thoughts > Re: Moving between folders > Re: big mailbox v.s. rotated mailbox; thoughts > charset in text/plain attachments: how to tune? > Re: ~A and the definition of "all" > Re: charset in text/plain attachments: how to tune? > Re: charset in text/plain attachments: how to tune? > Re: charset in text/plain attachments: how to tune? > Re: charset in text/plain attachments: how to tune? > Using message-hook to run messages through a filter > Re: Using message-hook to run messages through a filter > Re: Using message-hook to run messages through a filter > problem with timestamps > Re: new subject line format/threading > Mutt and Tiff's > Re: charset in text/plain attachments: how to tune? > Re: Using message-hook to run messages through a filter > Case sensitivity in regular expressions > Re: Case sensitivity in regular expressions > Re: Case sensitivity in regular expressions > Possible to add a user-defined field "Keyword" to read message before/when save? > Re: Possible to add a user-defined field "Keyword" to read message before/when >save? > Re: Possible to add a user-defined field "Keyword" to read message before/when >save? > Re: Configuration problems > Searching thru message headers? > Re: Possible to add a user-defined field "Keyword" to read message before/when >save? > Re: Searching thru message headers? > colorize messages in index older then x days > Re: colorize messages in index older then x days > Re: colorize messages in index older then x days > Re: colorize messages in index older then x days > > ---------------------------------------------------------------------- > > Date: Fri, 28 Dec 2001 09:03:16 +0100 > From: Markus Boelter <[EMAIL PROTECTED]> > Subject: Re: big mailbox v.s. rotated mailbox; thoughts > > - -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > On Thu, Dec 27, 2001 at 07:10:03PM -0700, Rob 'Feztaa' Park wrote: > > That's interesting, I guess I wouldn't mind a setup like that. Here's > > what I currently have, though, and I am happy with it: > > > > - procmail sorts all of my mail into various mboxes in ~/mail/ > > - mbox hooks are setup to move read mail into > > ~/mail/archives/YYYY-MM-mbox-name > My config is a little bit another: > I receive *all* my mails in /var/spool/mail/markus. With all mails I > also mean all the mailinglists I'm on. Now I made a macro in mutt which > sync's /var/spool/mail/markus. After syncing, the macro pipes all my > messages trough procmail and sort it in special folders, sortet by > mailinglists/people/Newsletters/spam/.. > So, if I start mutt, I can see all my new or read mails at one > moment and I haven't to browse through several folders. Aber reading > my macro sorts all the mails in the right folder. > This is my way to read and archive mails :) > So long! > Markus > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > iD8DBQE8LCdEz7FgOPsOHVsRAkM6AKC5r38ax6/14rsGWYRPipFWBKuk4gCfRgTk > ftAiDKJ6j5KoPqIZWSEblsY= > =qgFT > - -----END PGP SIGNATURE----- > > ------------------------------ > > Date: Fri, 28 Dec 2001 19:53:58 +0800 > From: Charles Jie <[EMAIL PROTECTED]> > Subject: 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 :) > > ------------------------------ > > Date: Fri, 28 Dec 2001 13:06:01 +0100 > From: Nicolas Rachinsky <[EMAIL PROTECTED]> > Subject: Re: big mailbox v.s. rotated mailbox; thoughts > > - --RnlQjJ0d97Da+TV1 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > 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~r>2w!~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>~d>2w\n<untag-pattern>~F|~D|~O|~N\n<tag-prefix-cond><save-message>\n\n<sync-mailbox><first-entry><next-new><redraw-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 > > - --RnlQjJ0d97Da+TV1 > Content-Type: application/x-sh > Content-Disposition: attachment; filename="move_mail.sh" > Content-Transfer-Encoding: quoted-printable > > #!/bin/sh=0A=0A=0A#=0A# Nicolas Rachinsky <[EMAIL PROTECTED]> =0A#=0A# BSD= > - -style copyright and standard disclaimer applies.=0A#=0A#=0A# first param= > is an mbox (optionally gzipped) =0A# second param is an mbox (optionally= > gzipped)=0A# if one of them is gzipped the name must end with .gz, = > if not it must not end with .gz=0A# third param is time offset for date (= > without leading "-")=0A# e.g. 2w or 3m=0A#=0A# minimal errorchecking=0A= > =0Aif [ $# !=3D 3 ]; then=0A echo "wrong parameters"=0A exit = > 1=0Afi=0A=0A=0Aif [ -e $1.tmp ];then=0A echo $1.tmp already exists=0A exit = > 1=0Afi=0A=0Acase $1 in=0A*.gz)=0A in_filter=3D"gzip -9"=0A;;=0A*.bz2)=0A in= > _filter=3D"bzip2"=0A;;=0A*)=0A in_filter=3D"cat"=0A;;=0Aesac=0A=0Acase $2 i= > n=0A*.gz)=0A out_filter=3D"gzip -9"=0A;;=0A*.bz2)=0A out_filter=3D"bzip2"= > =0A;;=0A*)=0A out_filter=3D"cat"=0A;;=0Aesac=0A=0Aswitchdate=3D"`date -v -$= > 3 '+%Y-%m-%d'`"=0Aif [ $? !=3D 0 ]; then=0A echo "Wrong third paramter"=0A = > exit 1=0Afi=0A=0Aif [ $2 !=3D /dev/null ]; then=0A touch $2 || { echo "coul= > dn't touch $2";exit 1; }=0A mutt_dotlock $2 || { echo "couldn't lock $2";ex= > it 1; }=0Afi=0A=0Amutt_dotlock $1 || { echo "couldn't lock $1";exit 1; }=0A= > =0Aif [ $2 !=3D /dev/null ]; then=0A (grepmail -a -d "before $switchdate" $= > 1 | $out_filter >>$2) || { echo "error appending to $2";exit 2;}=0Afi=0A=0A= > =0A(grepmail -a -v -d "before $switchdate" $1 | $in_filter >$1.tmp) || { ec= > ho "error appending to $1.tmp";exit 3;}=0A=0Amv -f $1.tmp $1||{ echo "error= > renaming $1.tmp to $1";exit 4;}=0A=0Aif [ $2 !=3D /dev/null ]; then=0A mut= > t_dotlock -u $2 || { echo "couldn't unlock $2";exit 1;}=0Afi=0Amutt_dotloc= > k -u $1 || { echo "couldn't unlock $1";exit 1;}=0A=0A > - --RnlQjJ0d97Da+TV1-- > > ------------------------------ > > Date: Fri, 28 Dec 2001 15:37:11 +0300 > From: boris karlov <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 13:41:54 +0100 > From: Michael Tatge <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 15:04:41 +0100 > From: Michael Tatge <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 17:28:29 +0300 > From: boris karlov <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 15:56:56 +0100 > From: Michael Tatge <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 18:48:56 +0300 > From: boris karlov <[EMAIL PROTECTED]> > Subject: 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. :) > > > > ------------------------------ > > Date: Fri, 28 Dec 2001 17:09:05 +0100 > From: Andre Majorel <[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". > - -- > André Majorel <URL:http://www.teaser.fr/~amajorel/> > std::disclaimer ("Not speaking for my employer"); > > ------------------------------ > > Date: Fri, 28 Dec 2001 17:15:32 +0100 > From: Nicolas Rachinsky <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 11:19:14 -0500 > From: Dan Boger <[EMAIL PROTECTED]> > Subject: Re: Using message-hook to run messages through a filter > > - --2fHTh5uZTiUOsy+g > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > 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 ? > >=20 > > I thought that=20 > >=20 > > message-hook "~f joe@blow\.com" "pipe-message /usr/local/bin/unmangle" > >=20 > > 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 > > - --=20 > Dan Boger > [EMAIL PROTECTED] > > - --2fHTh5uZTiUOsy+g > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iEYEARECAAYFAjwsm4IACgkQTN2f0twYwJiLMACfRSh51CN3A/NJmnMWA+uh0bJr > QggAnjQ7W18WjGZ+Vx5Dmxgs7Phv2lSu > =03gD > - -----END PGP SIGNATURE----- > > - --2fHTh5uZTiUOsy+g-- > > ------------------------------ > > Date: Fri, 28 Dec 2001 03:59:13 -0600 > From: Felipe Contreras <[EMAIL PROTECTED]> > Subject: 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? > > ------------------------------ > > Date: Fri, 28 Dec 2001 15:21:17 +0100 > From: martin f krafft <[EMAIL PROTECTED]> > Subject: Re: new subject line format/threading > > - --zhXaljGHf11kAtnf > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > 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. > > - --=20 > martin; (greetings from the heart of the sun.) > \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck > =20 > i'd give my right arm to be ambidextrous. > > - --zhXaljGHf11kAtnf > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iEYEARECAAYFAjwsf90ACgkQIgvIgzMMSnUk6wCgoQNo50b3disabcs+ZConiPh6 > ufoAn0Qy3AjV4TI3aQg/ZwTk+Hb5/VY8 > =1yIa > - -----END PGP SIGNATURE----- > > - --zhXaljGHf11kAtnf-- > > ------------------------------ > > Date: Fri, 28 Dec 2001 17:38:47 +0100 > From: Cliff Sarginson <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 17:55:55 +0100 > From: Michael Tatge <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 18:22:36 +0100 > From: Roman Neuhauser <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 17:17:27 +0000 > From: Benjamin Smith <[EMAIL PROTECTED]> > Subject: Case sensitivity in regular expressions > > - --FL5UXtIhxfXey3p5 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > 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. > > - --=20 > Benjamin Smith <[EMAIL PROTECTED], [EMAIL PROTECTED]> > > - --FL5UXtIhxfXey3p5 > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8LKkmT4wBnzJEg7URArEwAJ0bBVtKlrQrS95g4wMfXzKlH+ijSQCfdotH > l8XvuqlsFAkSC+q0AAn3K98= > =WaR6 > - -----END PGP SIGNATURE----- > > - --FL5UXtIhxfXey3p5-- > > ------------------------------ > > Date: Fri, 28 Dec 2001 12:40:26 -0800 > From: Gary Johnson <[EMAIL PROTECTED]> > Subject: Re: Case sensitivity in regular expressions > > On Fri, Dec 28, 2001 at 05:17:27PM +0000, 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/ | > > ------------------------------ > > Date: Fri, 28 Dec 2001 21:04:13 +0000 > From: Benjamin Smith <[EMAIL PROTECTED]> > Subject: Re: Case sensitivity in regular expressions > > - --jRHKVT23PllUwdXP > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Fri, Dec 28, 2001 at 12:40:26PM -0800, Gary Johnson wrote: > > On Fri, Dec 28, 2001 at 05:17:27PM +0000, 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. > >=20 > > >From the mutt manual: > >=20 > > 4.1. Regular Expressions > >=20 > > ... > >=20 > > The search is case sensitive if the pattern contains at least one > > upper case letter, and case insensitive otherwise. .... > >=20 > > 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. > > >=20 > > HTH, > > Gary > >=20 > > --=20 > > Gary Johnson | Agilent Technologies > > [EMAIL PROTECTED] | Spokane, Washington, USA > > http://www.spocom.com/users/gjohnson/mutt/ | > > - --=20 > Benjamin Smith <[EMAIL PROTECTED], [EMAIL PROTECTED]> > > - --jRHKVT23PllUwdXP > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8LN5MT4wBnzJEg7URAgC3AJ4uHhzPvJSdf78sRIsKN4X8eWNvSwCeI5OA > LQtKRvDfXq2dpsTLcWfjfJ0= > =7idt > - -----END PGP SIGNATURE----- > > - --jRHKVT23PllUwdXP-- > > ------------------------------ > > Date: Sat, 29 Dec 2001 11:17:51 +0800 > From: Charles Jie <[EMAIL PROTECTED]> > Subject: 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 > > ------------------------------ > > Date: Fri, 28 Dec 2001 21:28:34 -0700 > From: Rob 'Feztaa' Park <[EMAIL PROTECTED]> > Subject: Re: Possible to add a user-defined field "Keyword" to read message >before/when save? > > - --IS0zKkzwUGydFO0o > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > 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. > >=20 > > The purpose of it is that I want to give keywords or category to read mes= > sages so that I can search them easier later. > >=20 > > 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... > > - --=20 > 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) > > - --IS0zKkzwUGydFO0o > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8LUZyPTh2iSBKeccRAl/3AJwLXA0n9xMCX2iRYUeR2Plcqyf3jgCdFKSK > /GNJNpFTj6gc7+rUX6CYyLs= > =6z3h > - -----END PGP SIGNATURE----- > > - --IS0zKkzwUGydFO0o-- > > ------------------------------ > > Date: Fri, 28 Dec 2001 23:55:58 -0500 > From: "Justin R. Miller" <[EMAIL PROTECTED]> > Subject: Re: Possible to add a user-defined field "Keyword" to read message >before/when save? > > - --C7zPtVaVf+AK4Oqc > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Thus spake Charles Jie ([EMAIL PROTECTED]): > > > Obviously I don't mean 'e' (edit) command count. > >=20 > > The purpose of it is that I want to give keywords or category to read > > messages so that I can search them easier later. > >=20 > > 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... > > - --=20 > Justin R. Miller <[EMAIL PROTECTED]> > View my website at http://codesorcery.net > Please encrypt email using key 0xC9C40C31 > > - --C7zPtVaVf+AK4Oqc > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8LUze94d6K8nEDDERAgL2AJ46PVstKA0RotRSyUGiRhWX07a27QCeKdwu > 0emcYUjDi8Cb+Qq6apD6IIQ= > =U1X9 > - -----END PGP SIGNATURE----- > > - --C7zPtVaVf+AK4Oqc-- > > ------------------------------ > > Date: Sat, 29 Dec 2001 00:20:26 -0600 > From: David Rock <[EMAIL PROTECTED]> > Subject: Re: Configuration problems > > - --wLAMOaPNJ0fu1fTG > Content-Type: text/plain; charset=iso-8859-1 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Thu, Dec 27, 2001 at 02:17:53PM +0100, Ren=E9 Clerc wrote: > >=20 > > 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 ;-) > > - --=20 > David Rock > [EMAIL PROTECTED] > > - --wLAMOaPNJ0fu1fTG > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8LWCqLkT4RP62gz4RAm6FAJ9vW9NTfJ2c/phXolwCG0R93MxBpwCfb58z > nf4sEdEnawHPkvm2yRGnpgY= > =vng2 > - -----END PGP SIGNATURE----- > > - --wLAMOaPNJ0fu1fTG-- > > ------------------------------ > > Date: Fri, 28 Dec 2001 20:20:30 -0200 > From: Carlos Laviola <[EMAIL PROTECTED]> > Subject: Searching thru message headers? > > I know I can search thru message bodies, but how do I search thru > their headers? > Thanks, > Carlos. > - -- > _ _ _| _ _ | _ . _ | _ to hell with icq, use jabber! > (_(_|| |(_)_) |(_|\/|(_)|(_| THIS SPACE INTENTIONALLY LEFT BLANK? > > ------------------------------ > > Date: Sat, 29 Dec 2001 07:47:50 -0600 > From: David Champion <[EMAIL PROTECTED]> > Subject: Re: Possible to add a user-defined field "Keyword" to read message >before/when save? > > On 2001.12.28, in <[EMAIL PROTECTED]>, > "Charles Jie" <[EMAIL PROTECTED]> wrote: > > 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. :) > The X-Label: header is regonized for this purpose. %y expands it in the > index view, if you like, and ~y searches on it. It's supported in the > 1.3 series, but you need a patch for 1.2. > The basic support in 1.3 only provides recognition of the header, not > editing. (You edit it using edit-message.) Another patch provides a > binding (edit-label, 'y') to edit the header within mutt, with no > external editor. I find this much easier to use, personally. > All patches are at > http://home.uchicago.edu/~dgc/mutt#x-label > - -- > -D. [EMAIL PROTECTED] NSIT University of Chicago > > ------------------------------ > > Date: Sat, 29 Dec 2001 13:59:00 +0000 > From: [EMAIL PROTECTED] > Subject: Re: Searching thru message headers? > > - -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > On Fri, Dec 28, 2001 at 08:20:30PM -0200, Carlos Laviola wrote: > > I know I can search thru message bodies, but how do I search thru > > their headers? > > > > Thanks, > > Carlos. > > > > -- > > _ _ _| _ _ | _ . _ | _ to hell with icq, use jabber! > > (_(_|| |(_)_) |(_|\/|(_)|(_| THIS SPACE INTENTIONALLY LEFT BLANK? > - - From the manual: > 4.2. Patterns > ... > ~h EXPR messages which contain EXPR in the message header > ... > So type /~h<header(s) to search for> > - - -- > Benjamin Smith <[EMAIL PROTECTED], [EMAIL PROTECTED]> > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > iD8DBQE8LcwkT4wBnzJEg7URAmtLAKCXwfAtpo7mNsPJK520z/WxQC1LbgCfdkKX > PZWbbo7qERWQ57WHJkYUoec= > =z5CB > - -----END PGP SIGNATURE----- > > ------------------------------ > > Date: Sat, 29 Dec 2001 16:20:45 +0200 > From: Paulius Bulotas <[EMAIL PROTECTED]> > Subject: colorize messages in index older then x days > > Hello, > Is it possible to change colour of messages which are older by x days > then today? If yes, then how it's done? > Thanks, > Paulius > > ------------------------------ > > Date: Sat, 29 Dec 2001 08:42:46 -0600 > From: David Champion <[EMAIL PROTECTED]> > Subject: Re: colorize messages in index older then x days > > On 2001.12.29, in <20011229142045.GA78483@noname>, > "Paulius Bulotas" <[EMAIL PROTECTED]> wrote: > > Hello, > > > > Is it possible to change colour of messages which are older by x days > > then today? If yes, then how it's done? > Section 4.2.3 of the manual tells you. For example: > color index blazing-red murky-green "~r >5d" > - -- > -D. [EMAIL PROTECTED] NSIT University of Chicago > > ------------------------------ > > Date: Sat, 29 Dec 2001 15:48:53 -0500 > From: cruciatuz <[EMAIL PROTECTED]> > Subject: Re: colorize messages in index older then x days > > - --2oS5YaxWCcQjTEyO > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Sat, Dec 29, 2001 at 04:20:45PM +0200, Paulius Bulotas wrote: > =20 > > Is it possible to change colour of messages which are older by x days > > then today? If yes, then how it's done? > > color index magenta default '~r >1w' # Older than 1 wks > > for example. > > Stefan Antoni > - ---------------------------- > Sam Dez 29 15:47:39 EST 2001 > > - --2oS5YaxWCcQjTEyO > Content-Type: application/pgp-signature > Content-Disposition: inline > > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8Liw1XAdxjvauYZ4RAprhAKD6gs6JcUCrwJXSLKpkiDALqlD/6ACdHHSM > 7TfiA9vA7Bp6eWpTV+1RpOU= > =dw8K > - -----END PGP SIGNATURE----- > > - --2oS5YaxWCcQjTEyO-- > > ------------------------------ > > Date: Sat, 29 Dec 2001 14:53:20 +0000 > From: [EMAIL PROTECTED] > Subject: Re: colorize messages in index older then x days > > - -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > On Sat, Dec 29, 2001 at 08:42:46AM -0600, David Champion wrote: > > On 2001.12.29, in <20011229142045.GA78483@noname>, > > "Paulius Bulotas" <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > > > Is it possible to change colour of messages which are older by x days > > > then today? If yes, then how it's done? > > > > Section 4.2.3 of the manual tells you. For example: > > > > color index blazing-red murky-green "~r >5d" > Hmm, my mutt doesn't seem to like those colours. I wonder why? :-) > > > > -- > > -D. [EMAIL PROTECTED] NSIT University of Chicago > - - -- > Benjamin Smith <[EMAIL PROTECTED], [EMAIL PROTECTED]> > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > iD8DBQE8LdjfT4wBnzJEg7URApgcAJ9z9e0b9gBZveBn3vvUe0LnKzqczwCeLP2d > 3IMFOwp3MW+7bAR/XeRuQtA= > =arvt > - -----END PGP SIGNATURE----- > > ------------------------------ > > End of mutt-users-digest V1 #909 > ******************************** >
-- Nick Wilson Tel: +45 3325 0688 Fax: +45 3325 0677 Web: www.explodingnet.com
