Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-15 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday, February 15 at 10:47 AM, quoth Jan-Herbert Damm: With gratefulness an admiration i studied this manual-worthy explanation! Glad to help! In this case, the match-type-specifier is ~r. In the manual though they call it

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-15 Thread Jan-Herbert Damm
Hello, And Simple patterns seem to be specifically associated with certain keywords replacing ~,%,= expressions. Keywords? Replacing? No, the ~ or % or = don't get *replaced*. We must be talking past each other here. indeed, I was being unprecise. The manual (Chapter Advanced Usage)

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-15 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday, February 15 at 07:45 PM, quoth Jan-Herbert Damm: 2.2. Simple Patterns Mutt supports two versions of so called ``simple searches'' which are issued if the query entered for searching, limiting and similar operations does not seem

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-15 Thread Rocco Rutte
Hi, * Jan-Herbert Damm wrote: indeed, I was being unprecise. The manual (Chapter Advanced Usage) is saying this about simple *searches* not simple *patterns*. I still find it confusing if not contradictory, because the searching by keywords (= not valid patterns) is explained directly below

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-15 Thread Patrick Shanahan
* Rocco Rutte pd...@gmx.net [02-15-09 15:46]: Now we only need some new good headlines. How about simplified patterns and boolean operators and nesting. I'm thinking about re-ordering the sections so we first have simplified patterns, then pattern modifier and boolean operators and nesting

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-13 Thread Jan-Herbert Damm
Kyle Wheeler: ... However, because I use tag-prefix-cond, when there aren't any tagged messages (i.e. the pattern ~r 3m didn't match anything), mutt will stop processing that hook and none of the rest of it will happen. Does that make sense? yes it does! thank you so much for posting this

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-13 Thread John J. Foster
On Fri, 13 Feb 2009 19:20 +0100, Jan-Herbert Damm jan-h-d...@web.de wrote: Kyle Wheeler: ... However, because I use tag-prefix-cond, when there aren't any tagged messages (i.e. the pattern ~r 3m didn't match anything), mutt will stop processing that hook and none of the rest of it

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-13 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, February 13 at 07:20 PM, quoth Jan-Herbert Damm: if you don't mind, can you explain the pattern ~r 3m equally well? Well, that's pretty simple. First, mutt uses what it calls simple patterns to match messages. (That's what you search

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-12 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, February 12 at 08:15 PM, quoth John J. Foster: Am I nuts, or are these functionally equivalent? You're nuts. :) But they *are* very similar. Tag-prefix, of course, means that the next command will apply to all of the tagged messages.

Re: Clarification on tag-prefix-cond vs. tag-prefix

2009-02-12 Thread John J. Foster
On Thu, Feb 12, 2009 at 09:29:01PM -0600, Kyle Wheeler wrote: On Thursday, February 12 at 08:15 PM, quoth John J. Foster: Am I nuts, or are these functionally equivalent? You're nuts. :) But they *are* very similar. Tag-prefix, of course, means that the next command will apply to all of