While I'm glad you've got your syntax working, it is often easier (and more
flexible) to move tricky shell incantations off into a script.
As an example, I run a specialish vim incantation as my mutt editor. My muttrc
just says:
set editor=muttedit
and "muttedit" is a script in my bin directory, code here:
https://bitbucket.org/cameron_simpson/css/src/tip/bin/muttedit
It in turn sets editor to "vim-flowed", which is a small wrapper for vim that
puts it in a suitable mode for editing email with format-flowed:
https://bitbucket.org/cameron_simpson/css/src/tip/bin/vim-flowed
Stuff all that directly into a muttrc would be painful and near impossible to
debug, at the least.
Writing yourself a special purpose shell script makes your muttrc simple and
puts the code somewhere where it doesn't need lots of nested escaping.
Just a thought.
Cheers,
-- Cameron Simpson <c...@zip.com.au>
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it. - Brian W. Kernighan
