On Feb 21, Daniel Eisenbud [[EMAIL PROTECTED]] wrote: > On Thu, Feb 21, 2002 at 02:52:57PM +0000, Bruno Postle <[EMAIL PROTECTED]> wrote: > > On Thu 21-Feb-2002 at 03:28:48PM +0100, Alexander Skwar wrote: > > > > > > Hmm, but how to do this? Sometimes, messages don't contain my > > > message-id in the References, aren't To: or Cc: me (eg. a message > > > "far" down in the thread), but mutt will still show that it belongs to > > > a given thread. > > > > You can't with the current 'limit' command. A context-limit ability > > (like grep -C) would be a useful refinement to mutt though. > > > > In fact, most of the time I use 'limit' I would prefer to use a more > > general context-with-threads-limit than the current behaviour. I often > > find myself limiting to a pattern, picking a message, showing everything > > to see the thread, limiting again, picking a message etc.. > > Hmm, maybe a tag-pattern-threads and a limit-pattern-threads command?
I think some pattern matching modifiers would be more general purpose: - one for 'all messages in the same thread as a message that matches this pattern' - one for 'parent message of the thread of a message that matches this pattern' - one for 'all children of a message that matches this pattern' These can all be used for tag-pattern and limit-pattern, but also for colors, etc. I guess there aren't actually any pattern match modifiers in the real source, but there are several patches to add these, and they are useful. There's even one that already does the last one above, but the other two are the ones I usually want, especially the first; it'd be nice to be able to view threads while they are collapsed and still see that a thread had a flagged message, or color it when it contains new messages (it does get the small 'n' but colors are easier to see, esp when other new messages are colored). The kind of thing mentioned in <http://bugs.guug.de/db/40/408.html> seems really useful to me, but I'd rather see it based on pattern matching. > Sounds useful to me, and relatively easy to implement. As it is, I > usually limit, and do tag-thread on each visible message, and then limit > to tagged, which works but is kind of a pain. It also is odd to me it works... you can affect messages you can't actually see using tag-thread, but not otherwise? (The one that always bites me is when I enter a big mailbox with threads collapsed by default, read the stuff I want, then try to do <delete-pattern>~N without uncollapsing threads first.)
msg24641/pgp00000.pgp
Description: PGP signature
