#2969: new function: lock-tag-prefix
Comment (by Nicolas Rachinsky):
{{{
* Mutt <[EMAIL PROTECTED]> [2007-10-11 07:41 -0000]:
> > 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.
I think this can cause hard to debug problems. If the user notes that
there is a problem, since the problem will look like strange
unreproducable behaviour.
> > Does it work with nested macros?
>
> I would think it does, but untested and I'm not a mutt expert.
I just noted that the patches in the mentioned thread do not handle
nested macros well if more than one uses <tag-push>/<tag-set-tagflag>.
:(
> > 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.
Yes, that's the idea.
Nicolas
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/2969#comment:>
