Le mardi 28 août 2007 à 22:50:12 +0200, Loïc Minier écrivait:
> unfortunately, [pager's <flag-message>] only works for the
> "important" flag
The pager has functions for manipulating many flags:
| flag key function help
|---------------------------------------------------------------------------
| ! F <flag-message> toggle a message's 'important' flag
| N N <mark-as-new> toggle a message's 'new' flag
| D d <delete-message> delete the current entry
| D u <undelete-message> undelete the current entry
| * t <tag-message> tag the current entry
|---------------------------------------------------------------------------
Only "O" and "r" flags seemingly lack (unless <reply> counts ;-).
> and has the side effect of moving to the next message (I guess that's
> a feature).
Feature controlled by the $resolve switch, on by default.
[<exit><set-flag>]
> Hmm that's not very practical; I simply want to toggle a flag, not
> stop reading the message. :-/
Well, anyway <set-flag> $resolves to the next message, by default.
So my macros and pager:<set-flag> would equally stop you from reading
the current message. Granted, pager:<set-flag> would stay in pager,
while my macros eject you to the index. Hum... what about:
| macro pager <F42> <exit><set-flag>O<display-message> "mark message
Old"
| macro pager <F43> <exit><clear-flag>O<display-message> "mark message
read"
Unfortunately it's not possible to prompt the user in the middle of
a macro. The macro has to embed the response.
> These are certainly helpful workarounds, but it seems to me it would
> be very natural to have "clear-flag" and "set-flag" available
Natural, I agree. OTOS this would mean more code. And a longer list
of functions, when we already have so many that users may be lost.
Adding code, <funcs>, and $vars should be done primarily for interesting
new features not doable otherwise. My opinion is not done yet: I'd need
to hear more arguments, and think to it.
Bye! Alain.
--
How to Report Bugs Effectively
<URL:http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
