On 24 Oct 2026 20:46 -0500, from [email protected] (Tim Chase): > T~U;Wn > > which translates roughly as > > <tag-pattern>~U (tags the unread messages) > <tag-prefix> (apply the following command to those tagged messages) > <clear-flag>n (clear the New/Unread flag) > > so you *should* be able to wrap that all up > > <tag-pattern>~U<tag-prefix><clear-flag>n > > in a macro under whatever key you prefer.
Wouldn't you need a <enter> before the <tag-prefix> to terminate input? Also, I'm pretty sure you can't have key chords in a macro like Ranjan is trying, so mutt might be bailing out at the <C-v> or possibly just erroring out on that part and then the rest of the macro clears the error message. Since both of these are pretty short and simple as mutt macros go, one way would be to start with just the first command _in a macro_, try that, then add them back one by one until you see what the problem is. You can use <enter-command> (bound to `:` by default) to re-run the `macro` command to re-bind on the fly. Keep in mind that muttrc generally needs another layer of quoting. And yes, in macros, it's better to use the <command-names> rather than the particular key binding. It makes the macro more readable and less likely to break in unexpected ways if you decide to rebind keys. Ctrl+v doesn't _seem_ to be a standard key binding, at least (but I could be wrong on that). -- Michael Kjörling 🔗 https://michael.kjorling.se
