Re: tagging and saving a collapsed thread -> Bug?
Jussi Ekholm <ekhowl <at> goa-head.org>
2002-11-01 00:55:52 GMT
René Clerc <rene <at> clerc.nl> wrote:
> The thing that hurts me is that it is possible to tag a collapsed
> thread (i.e. all messages inside are indeed tagged), but the
> subsequent operation that is performed on the tagged messages
> doesn't affect all tagged messages. Conceptually, this hurts ;)
I agree completely. It's an utter annoyance, as I first tag a whole
thread (<Esc-Shift-t>) and then give 'n' for tag-prefix, and only
the first message is marked (un)read. Of course, there's <Ctrl-r> for
marking a thread read, but it would be nice to easily mark threads
_un_read, as well.
Ah well, I guess I have to put up a macro, that first collapses the
thread, then tags it, does the thing it's supposed to and collapses
the thread again. Shouldn't be too hard, either...
>> I understand the technical reason for the behavior, but my guess is
>> that 99% of users want it the other way.
> Count me in.
Yeah, I don't like this visible/invisible thing, either. When I want
to tag a whole thread unread, it's a bit of hard even as I have
command 'tag-thread' and I can give 'n' as tag-prefix. Macro I shall
(and have to) use.
Jussi Ekholm <ekhowl <at> goa-head.org> | <http://erppimaa.ihku.org/> | <0x1410081E>