for each nested lvl of cmds as args to cmds you must add an extra lvl of quoting for
lvl: not all chars are special on every lvl.
Side-effects by other config files:
a global Muttrc with bad defaults for all users: "mutt -v | grep SYSCONFDIR" to find it.
user files sourced by macros or hooks possibly overwriting vars, when the ":set ?var" check fails.
Side-effects by 3rd party patches: retry with native
mutt before asking the wrong people, ask patch provider if it's patch-related.
Features not enabled in binary: see MuttGuide/Setup to figure out which are enabled and whether you need to build a new binary.
Special treatment of '\' line continuation with '#' comments per MuttGuide/Syntax:
if you comment lines, make sure you hit the beginning and don't break or oversee -continuations, especially with hooks.
Macros badly defined:
use "<>" notation for functions rather than keystrikes, allows to better detect typos and more portable.
remember: macros are a replay of keystrikes you'd normally type manually: always check whether the sequence works manually with each
Confusion about use of "set from=..." and "my_hdr", see MuttFaq/Header.
"my_hdr" has some issues when interacting with "send-hook" for example, read docs about both.
Sometimes the problem is not the config but the code: update to the most
recent developer version and retry. This way you exclude problems with
your old version that might have been fixed in the meantime. See also
reported errors in the bug tracking system.
Always remember to have a look at MuttFaq if you get stuck somewhere.