#2969: new function: lock-tag-prefix
Comment (by Lionel Elie Mamane):
{{{
On Thu, Oct 11, 2007 at 07:26:26AM -0000, Mutt wrote:
> * Mutt <[EMAIL PROTECTED]> [2007-10-11 06:38 -0000]:
>> lock-tag-prefix lock the tag-prefix to "on", but only if it is in
effect.
>> unlock-tag-prefix unlocks it.
> What happens if the macro aborts before it reaches the
> unlock-tag-prefix?
The tag-prefix stays locked, and there is no visible cue to the user
that it is so. I don't know how to add such a visible cue.
> Does it work with nested macros?
I would think it does, but untested and I'm not a mutt expert.
> And you can't apply the tag-prefix to only some of the commands in
> the macro with your patch, I think.
That is mostly correct. You can apply it to some commands, and then
not apply it to the commands that come after that, but you cannot
apply to commands after that. I.e. you can do:
<lock-tag-prefix>cmd1 cmd2 cmd3<unlock-tag-prefix>cmd4 cmd5 cmd6
and the tag-prefix will be applied to commands 1, 2 and 3, but not 4,
5 and 6.
> There are two similar patches in the thread on mutt-dev starting with
> <[EMAIL PROTECTED]>.
From skimming the first of these patches, it seems to me that to get
the effect I'm after, you'd have to do something like:
<tag-push><tag-pop>cmd1<tag-pop>cmd2<tag-pop>cmd3
Yeah, I'd be happy with that, too.
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/2969#comment:>
