Re: rewriting message stautus
On Mon, Jan 28, 2002 at 08:38:45PM -0600, Jeremy Blosser wrote: Yeah, you can do some great stuff with that. My own settings do the following: Sounds great, maybe you could send part of your muttrc responsible for such colors? -- _.|._ |_ _. | Adam Byrtek, [EMAIL PROTECTED] (_|||_)| |(_| | gg 1802819 |
Re: rewriting message stautus
On Jan 29, [EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote: On Mon, Jan 28, 2002 at 08:38:45PM -0600, Jeremy Blosser wrote: Yeah, you can do some great stuff with that. My own settings do the following: Sounds great, maybe you could send part of your muttrc responsible for such colors? Heh, here. There are some comments at the top about the verbosity of the way it's done. Also, if you pay attention to the colors specified you'll notice the bright ones aren't in the same format as the others... this is because I changed the behaviour on mine to use inverse for bold background so that I can get some more colors than I could otherwise. ### Index coloring. These are all much more specific than they need to be ### since only the last matching will have an affect, but hopefully that will ### get fixed at some point. Being able to have attributes cascade would ### also make this all easier in general. # regular new messages color index black white ~N !~T !~F !~p !~P # regular tagged messages color index default white ~T !~F !~p !~P # regular flagged messages color index default red ~F !~p !~P # messages to me color index yellow default ~p !~N !~T !~F !~P color index default yellow ~p ~N !~T !~F !~P color index yellow white ~p ~T !~F !~P color index yellow red ~p ~F !~P # messages from me color index green default ~P !~N !~T !~F color index default green ~P ~N !~T !~F color index green white ~P ~T !~F color index green red ~P ~F # messages which mention my name in the body color index yellow default ~b \[Bb]losser[ @]\ !~N !~T !~F !~p !~P color index default yellow ~b \[Bb]losser[ @]\ ~N !~T !~F !~p !~P color index yellow white ~b \[Bb]losser[ @]\ ~T !~F !~p !~P color index yellow red ~b \[Bb]losser[ @]\ ~F !~p !~P # messages which are in reference to my mails color index magenta default ~x shade.firinn.org !~N !~T !~F !~p !~P color index default magenta ~x shade.firinn.org ~N !~T !~F !~p !~P color index magenta white ~x shade.firinn.org ~T !~F !~p !~P color index magenta red ~x shade.firinn.org ~F !~p !~P # messages to root, etc. color index blue default ~C \(root|postmaster|abuse|mailer-daemon)@\ !~N !~P !~p color index default blue ~C \(root|postmaster|abuse|mailer-daemon)@\ ~N !~P !~p # messages from known aliases (requires dgc.isalias) color index cyan default @~f . !~N !~T !~F !~P color index default cyan @~f . ~N !~T !~F !~P color index cyan white @~f . ~T !~F !~P color index cyan red @~f . ~F !~P # messages from my wife color index brightblue default ~f mywifesemail !~N !~T !~F color index brightblue brightwhite ~f mywifesemail ~N !~T !~F color index brightblue white ~f mywifesemail ~T !~F color index brightblue red ~f mywifesemail ~F # bigass messages color index red default !~N ~z 10240- # deleted messages color index brightblack default ~D msg23952/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
On Tue, Jan 29, 2002 at 09:35:26AM -0600, Jeremy Blosser wrote: Sounds great, maybe you could send part of your muttrc responsible for such colors? Heh, here. There are some comments at the top about the verbosity of the way it's done. Thanks a lot, BTW I'm still being amazed by mutt's capabilities... -- _.|._ |_ _. | Adam Byrtek, [EMAIL PROTECTED] (_|||_)| |(_| | gg 1802819 |
Re: rewriting message stautus
On 28/01/02, from the brain of Justin R. Miller tumbled: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Nicholas A. Martini ([EMAIL PROTECTED]): folder-hook lists 'color index brightmagenta default ~x mithrandir.codesorcery.net !~P' Can you explain how this works? I think I can use it to Flag entire threads if they have any Flagged messages in them. But I'm a bit new and I don't understand the syntax. -- Michael Montagne [EMAIL PROTECTED] http://www.boora.com
Re: rewriting message stautus
On Jan 29, Michael Montagne [[EMAIL PROTECTED]] wrote: folder-hook lists 'color index brightmagenta default ~x mithrandir.codesorcery.net !~P' Can you explain how this works? It matches if the References: header (specified by the ~x pattern) contains the pattern mithrandir.codesorcery.net, and the message is not from me (the !~P pattern... I believe in this case me is Justin Miller). See section 4.2 in TFM. I think I can use it to Flag entire threads if they have any Flagged messages in them. But I'm a bit new and I don't understand the syntax. No, unfortunately there are no patterns that allow you to match messages other than one at a time. There is a patch out there that allows you to match children of a given match, but not quite what you're looking for. msg23966/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
in message [EMAIL PROTECTED], wrote parv thusly... in message [EMAIL PROTECTED], wrote Justin R. Miller thusly... ... folder-hook . push 'T~N~P\n;N\n\ct.\n' Note that this is untested, but what I think I'm trying to do is, upon entering a folder, tag all new messages that were written by me, then toggle their new status, then untag all messages. ... # next three lines should be one; # wrapped for email macro index Escz \ 'tag-pattern ~Pentertag-prefixclear-flagNuntag-pattern ~Penter' \ mark messages read sent by me # # after defining key binding, make it execute for every folder folder-hook . 'push \ez' ... there is a problem w/ jrm's version, and will be w/ my version if tag-pattern is changed from ~P to ~N~P. problem is when no ~N~P messages are found, tag-prefix fails. then regardless of tag-prefix failure, N flag is toggled, or cleared, of the first new/unread message. - parv --
Re: rewriting message stautus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake parv ([EMAIL PROTECTED]): there is a problem w/ jrm's version, and will be w/ my version if tag-pattern is changed from ~P to ~N~P. problem is when no ~N~P messages are found, tag-prefix fails. then regardless of tag-prefix failure, N flag is toggled, or cleared, of the first new/unread message. Good call. Without conditional checking (which is lacking in Mutt), I don't know of a way around this... - -- [!] Justin R. Miller [EMAIL PROTECTED] PGP 0xC9C40C31 -=- http://codesorcery.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8VwU894d6K8nEDDERAmdbAJ9ZGGqGX2lc6N9pDqx4R4e6T/AbGgCfahFn riGy7OmzRwcsz1s0L9Z693M= =sHHd -END PGP SIGNATURE-
Re: rewriting message stautus
* On Tue, Jan 29, 2002 at 03:25:32PM -0500, * Justin R. Miller [EMAIL PROTECTED] wrote: Thus spake parv ([EMAIL PROTECTED]): problem is when no ~N~P messages are found, tag-prefix fails. then regardless of tag-prefix failure, N flag is toggled, or cleared, of the first new/unread message. Good call. Without conditional checking (which is lacking in Mutt), I don't know of a way around this... http://www.rachinsky.de/nicolas/mutt.html patch-1.3.23.2.nr.tag_prefix_cond works for me Nicolas
Re: rewriting message stautus
Hi, On Mon, 28 Jan 2002 Jeremy Blosser spewed into the ether: On Jan 28, Nicholas A. Martini [[EMAIL PROTECTED]] wrote: does anyone know how to make mutt show messages from yoursef (or another address) show up as read, or not new, or something? it would be handy for high-volume lists. depends... if you mean to do it at any given time, use: T (tag-pattern) some pattern (see the manual...mails from yourself would be ~P) enter ; (tag-prefix) W (clear-flag) N And you could 'push' this entire macro everytime you enter said folder. pv. -- Prahlad Vaidyanathan [EMAIL PROTECTED] I'm having a BIG BANG THEORY!!
Re: rewriting message stautus
in message [EMAIL PROTECTED], wrote Nicolas Rachinsky thusly... * On Tue, Jan 29, 2002 at 03:25:32PM -0500, * Justin R. Miller [EMAIL PROTECTED] wrote: Thus spake parv ([EMAIL PROTECTED]): problem is when no ~N~P messages are found, tag-prefix fails. then regardless of tag-prefix failure, N flag is toggled, or cleared, of the first new/unread message. Good call. Without conditional checking (which is lacking in Mutt), I don't know of a way around this... http://www.rachinsky.de/nicolas/mutt.html patch-1.3.23.2.nr.tag_prefix_cond i was avoiding the patch. but now that even w/ ~P pattern, i had above mentioned problem; so i will try this patch w/ 1.3.27i... on a side note, is this patch, or something similar, will make/has made into the mutt(-devel) source tree? - parv --
Re: rewriting message stautus
in message [EMAIL PROTECTED], wrote parv thusly... in message [EMAIL PROTECTED], wrote Nicolas Rachinsky thusly... * Justin R. Miller [EMAIL PROTECTED] wrote: ... Without conditional checking (which is lacking in Mutt), I don't know of a way around this... http://www.rachinsky.de/nicolas/mutt.html patch-1.3.23.2.nr.tag_prefix_cond ... i was avoiding the patch. but now that even w/ ~P pattern, i had above mentioned problem; so i will try this patch w/ 1.3.27i... well, w/ the patch, this... macro index EscZ \ 'tag-pattern~N~Pentertag-prefix-condclear-flagNuntag-pattern~Penter' # folder-hook . 'push \eZ' ...works w/o problems now. thanks nicolas. --
rewriting message stautus
the topic is for lack of a better discription. does anyone know how to make mutt show messages from yoursef (or another address) show up as read, or not new, or something? it would be handy for high-volume lists. nk -- Nicholas A. Martini [Autonomous Drone #AD-2918787-REJ] Redhat Certified Engineer[#807101313203345] http://www.devaluate.com [[EMAIL PROTECTED]] [cynical: a word used by the frightened to describe the realistic]
Re: rewriting message stautus
On Jan 28, Nicholas A. Martini [[EMAIL PROTECTED]] wrote: does anyone know how to make mutt show messages from yoursef (or another address) show up as read, or not new, or something? it would be handy for high-volume lists. depends... if you mean to do it at any given time, use: T (tag-pattern) some pattern (see the manual...mails from yourself would be ~P) enter ; (tag-prefix) W (clear-flag) N If you want this always true for these mails, Mutt won't do it. You'd want to use procmail or something to change the status flags as the messages arrive. msg23930/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Nicholas A. Martini ([EMAIL PROTECTED]): does anyone know how to make mutt show messages from yoursef (or another address) show up as read, or not new, or something? it would be handy for high-volume lists. Well, as for something, I use these settings: folder-hook . 'color index brightblue default ~P' folder-hook sent 'uncolor index brightblue default ~P' folder-hook . 'uncolor index brightmagenta default ~x mithrandir.codesorcery.net !~P' folder-hook lists 'color index brightmagenta default ~x mithrandir.codesorcery.net !~P' folder-hook lists 'color index green default ~p' Which has the effect of showing mail from me as brightblue (except in my sent folder, which is unnecessary), threads that I've been a part of as brightmagenta, and mail sent directly to me but that ends up in a list folder as green so as to distinguish it further from list mail (aside from the to_chars markings). Have fun! - -- [!] Justin R. Miller [EMAIL PROTECTED] PGP 0xC9C40C31 -=- http://codesorcery.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8VgZv94d6K8nEDDERAjcfAKCE6HO9Uvt4dQbHCpEZoY4tggO+7ACgkJ+u o34U0SOmwpER4NvSpxh2RGE= =UDtB -END PGP SIGNATURE-
Re: rewriting message stautus
On Jan 28, Justin R. Miller [[EMAIL PROTECTED]] wrote: Thus spake Nicholas A. Martini ([EMAIL PROTECTED]): does anyone know how to make mutt show messages from yoursef (or another address) show up as read, or not new, or something? it would be handy for high-volume lists. Well, as for something, I use these settings: folder-hook . 'color index brightblue default ~P' folder-hook sent 'uncolor index brightblue default ~P' folder-hook . 'uncolor index brightmagenta default ~x mithrandir.codesorcery.net !~P' folder-hook lists 'color index brightmagenta default ~x mithrandir.codesorcery.net !~P' folder-hook lists 'color index green default ~p' Which has the effect of showing mail from me as brightblue (except in my sent folder, which is unnecessary), threads that I've been a part of as brightmagenta, and mail sent directly to me but that ends up in a list folder as green so as to distinguish it further from list mail (aside from the to_chars markings). Yeah, you can do some great stuff with that. My own settings do the following: foreground colors: - mails to me are foreground yellow (even in my non-list boxes...helps make spam easy to visually identify) - mails from me are foreground green - mails in a thread I've participated in are foreground magenta - mails to me from a known alias are foreground cyan (I use this and my alias list to basically flag interesting people) - mails from certain particular people get their own color background colors: - normal mails are background default - new mails invert the regular colors (so new mails to me are background yellow, foreground default) - tagged mails are background white - flagged mails are background red a few special cases that override other colors: - messages bigger than 10k are red on default - deleted mails are brightblack on default My wife looks at my mail desktop and thinks I'm nuts, but it saves a heckuva lot of unnecessary scanning. msg23932/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Justin R. Miller ([EMAIL PROTECTED]): Thus spake Nicholas A. Martini ([EMAIL PROTECTED]): does anyone know how to make mutt show messages from yoursef (or another address) show up as read, or not new, or something? it would be handy for high-volume lists. Well, as for something, I use these settings: snip color settings I just now realized that I think you're not trying to colorize or otherwise indicate messages from you, but instead just mark them read. Maybe something like this: folder-hook . push 'T~N~P\n;N\n\ct.\n' Note that this is untested, but what I think I'm trying to do is, upon entering a folder, tag all new messages that were written by me, then toggle their new status, then untag all messages. Whether the above will accomplish that or not is another issue altogether... ;-) - -- [!] Justin R. Miller [EMAIL PROTECTED] PGP 0xC9C40C31 -=- http://codesorcery.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Vhj994d6K8nEDDERAgu7AJwLkURAZWlZ0iNv1UvGHwLV90mvAgCfdehY zCOAxvyDavJamkS7SB6gWT0= =DlGZ -END PGP SIGNATURE-
Re: rewriting message stautus
On Mon, Jan 28, 2002 at 10:37:34PM -0500, Justin R. Miller wrote: I just now realized that I think you're not trying to colorize or otherwise indicate messages from you, but instead just mark them read. Maybe something like this: folder-hook . push 'T~N~P\n;N\n\ct.\n' Note that this is untested, but what I think I'm trying to do is, upon entering a folder, tag all new messages that were written by me, then toggle their new status, then untag all messages. Whether the above will accomplish that or not is another issue altogether... ;-) - -- [!] Justin R. Miller [EMAIL PROTECTED] Won't this result in previously untagged becoming tagged ?? -- Pat Shanahan Registered Linux User #207535 Registered at: http://counter.li.org
Re: rewriting message stautus
Justin -- ...and then Justin R. Miller said... % % -BEGIN PGP SIGNED MESSAGE- % Hash: SHA1 % % Thus spake Justin R. Miller ([EMAIL PROTECTED]): % % Thus spake Nicholas A. Martini ([EMAIL PROTECTED]): % % does anyone know how to make mutt show messages from yoursef (or % another address) show up as read, or not new, or something? it would % be handy for high-volume lists. I'd use procmail and formail, BTW. % % Well, as for something, I use these settings: % % snip color settings % % I just now realized that I think you're not trying to colorize or % otherwise indicate messages from you, but instead just mark them read. % Maybe something like this: % % folder-hook . push 'T~N~P\n;N\n\ct.\n' % % Note that this is untested, but what I think I'm trying to do is, upon % entering a folder, tag all new messages that were written by me, then % toggle their new status, then untag all messages. You'd want to clear the new flag instead of toggle it, or when he entered the folder a second time all of his old new messages would be new and then his new new messages would be old, and then next time... Meanwhile, this is the sort of thing that's good with Nicolas's tag_conditional patch. % % Whether the above will accomplish that or not is another issue % altogether... ;-) Yeah, I'm not even going that far :-) It *looks* right, but I haven't tested it, either. % % - -- % [!] Justin R. Miller [EMAIL PROTECTED] % PGP 0xC9C40C31 -=- http://codesorcery.net HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg23937/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
On Jan 28, David T-G [[EMAIL PROTECTED]] wrote: ...and then Justin R. Miller said... % folder-hook . push 'T~N~P\n;N\n\ct.\n' You'd want to clear the new flag instead of toggle it, or when he entered the folder a second time all of his old new messages would be new and then his new new messages would be old, and then next time... Meanwhile, this is the sort of thing that's good with Nicolas's tag_conditional patch. I had the same thought initially, but since he's got the ~N in his pattern for tagging, it won't actually have that problem. msg23938/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
Jeremy Justin -- ...and then Jeremy Blosser said... % % On Jan 28, David T-G [[EMAIL PROTECTED]] wrote: % ...and then Justin R. Miller said... % % folder-hook . push 'T~N~P\n;N\n\ct.\n' % % You'd want to clear the new flag instead of toggle it, or when he entered ... % % I had the same thought initially, but since he's got the ~N in his pattern % for tagging, it won't actually have that problem. Oooh; good point! Way to go, both of you. :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg23939/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
in message [EMAIL PROTECTED], wrote Justin R. Miller thusly... Thus spake Nicholas A. Martini ([EMAIL PROTECTED]): does anyone know how to make mutt show messages from yoursef (or another address) show up as read, or not new, or something? it would be handy for high-volume lists. ... just mark them read. Maybe something like this: folder-hook . push 'T~N~P\n;N\n\ct.\n' Note that this is untested, but what I think I'm trying to do is, upon entering a folder, tag all new messages that were written by me, then toggle their new status, then untag all messages. when you want something done, you have to do it yourself. enough w/ all the fudging! given all the guesses flying around, i fed up and tried on my own. so here it is... # next three lines should be one; # wrapped for email macro index Escz \ 'tag-pattern ~Pentertag-prefixclear-flagNuntag-pattern ~Penter' \ mark messages read sent by me # # after defining key binding, make it execute for every folder # folder-hook . 'push \ez' ...i tried to put the whole macro in to the folder hook; but i kept getting unknown command w/... folder-hook . 'tag-pattern' ...and too many arguments w/ ... folder-hook . 'push T~P' ...so i resorted to create a key binding and execute it as shown. given above quoted folder-hook syntax, it seems now that i may not be using the right syntax for push. however the given push syntax seems too cryptic to follow w/o a manual on hand. - parv --
Re: rewriting message stautus
On Jan 29, parv [[EMAIL PROTECTED]] wrote: when you want something done, you have to do it yourself. enough w/ all the fudging! given all the guesses flying around, i fed up and tried on my own. so here it is... Er, what fudging? What you have is pretty much identical to what was suggested. Oh well. # next three lines should be one; # wrapped for email macro index Escz \ 'tag-pattern ~Pentertag-prefixclear-flagNuntag-pattern ~Penter' \ mark messages read sent by me # # after defining key binding, make it execute for every folder # folder-hook . 'push \ez' ...i tried to put the whole macro in to the folder hook; but i kept getting unknown command w/... folder-hook . 'tag-pattern' Yes, because folder-hooks can only take commands. tag-pattern is a function. push is a command. You need 'push tag-pattern...' ...and too many arguments w/ ... folder-hook . 'push T~P' This is probably because you have multiple matching folder-hooks w/push or something, and you don't have an enter in there, so they all end up in the same keyboard buffer and manage to create an illegal command. msg23941/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
in message [EMAIL PROTECTED], wrote Justin R. Miller thusly... ... I just now realized that I think you're not trying to colorize or otherwise indicate messages from you, but instead just mark them read. Maybe something like this: folder-hook . push 'T~N~P\n;N\n\ct.\n' Note that this is untested, but what I think I'm trying to do is, upon entering a folder, tag all new messages that were written by me, then toggle their new status, then untag all messages. i tried the above which works (1.3.25i), or at least worked once. can anybody enlighten me why the variation below does not? folder-hook . push 'T~N~P\n;\efN\cT~P\n' ...where... bind index \ef clear-flag bind index \cT untag-pattern ...all this hook is does is tag the ~N~P message. it does not go beyond that. - parv --
Re: rewriting message stautus
in message [EMAIL PROTECTED], wrote Jeremy Blosser thusly... On Jan 29, parv [[EMAIL PROTECTED]] wrote: ... enough w/ all the fudging! given all the guesses flying around, i fed up and tried on my own. so here it is... Er, what fudging? What you have is pretty much identical to what was suggested. Oh well. well, the solution (folder-hook ... push ...) came w/ untested disclaimer; and before that color options were being discussed... so... i suppose i was rather quick to reply w/o much thinking. ...i tried to put the whole macro in to the folder hook; but i kept getting unknown command w/... folder-hook . 'tag-pattern' Yes, because folder-hooks can only take commands. tag-pattern is a function. push is a command. You need 'push tag-pattern...' okay will try that too... ...and too many arguments w/ ... folder-hook . 'push T~P' This is probably because you have multiple matching folder-hooks w/push or something, and you don't have an enter in there, so they all end up in the same keyboard buffer and manage to create an illegal command. ...thanks much for both the explanations. - parv --
Re: rewriting message stautus
On Jan 29, parv [[EMAIL PROTECTED]] wrote: in message [EMAIL PROTECTED], wrote Justin R. Miller thusly... folder-hook . push 'T~N~P\n;N\n\ct.\n' i tried the above which works (1.3.25i), or at least worked once. can anybody enlighten me why the variation below does not? folder-hook . push 'T~N~P\n;\efN\cT~P\n' bad quoting... use folder-hook . 'push T~N~P\n;\efN\cT~P\n' msg23944/pgp0.pgp Description: PGP signature
Re: rewriting message stautus
in message [EMAIL PROTECTED], wrote Jeremy Blosser thusly... On Jan 29, parv [[EMAIL PROTECTED]] wrote: in message [EMAIL PROTECTED], wrote Justin R. Miller thusly... folder-hook . push 'T~N~P\n;N\n\ct.\n' i tried the above which works (1.3.25i), or at least worked once. can anybody enlighten me why the variation below does not? folder-hook . push 'T~N~P\n;\efN\cT~P\n' bad quoting... use folder-hook . 'push T~N~P\n;\efN\cT~P\n' that solved the problem. now both the keys/commands and the functions versions are working as expected. thanks much. - parv --
