On Sat, Mar 27, 2021 at 08:19:51PM +0100, Andy Spiegl wrote:
I just noticed an interesting detail - or is it a bug?When I run <pipe-message> in the attachment menu mutt behaves like <pipe-entry> and only pipes the selected part.
<pipe-message> isn't defined in the attachment menu, only <pipe-entry> is. You can check this by trying to run ":exec pipe-message" in the attachment menu.
However, internally they are bound to the same op-code (OP_PIPE). So in some cases, such as the push or macro commands, you can get away with using either. This is because push/macro try to tokenize angle-bracketed functions and convert them to an op-code in a menu-agnostic manner; the whole string, including ops are then buffered and executed later.
OTOH, exec only accepts function arguments, so it looks them up using the active menu.
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
