Hi Antonio, > since many things changed in teh most recent version (including the fact that > we are not using neomutt anymore), are you still experiencing this issue in > 1.14.4-2?
I’ve just tested using mutt package 1.14.5-1 using the small muttrc from the mail that opened this bug report, the main bug reported is still there. Namely "<function-name>" in a macro sequence is interpreted as a call to the function if the function is available in the current context and but otherwise as a sequence of the keys '<', 'f', etc. So this bug is still present. I cannot reproduce the other, tiny, bug, about some part of the sequence not being interpreted after a <shell-escape>, though. Best regards, Samuel
