* Marco <net...@lavabit.com> [2013-01-11 20:12:11 +0100]: > On 2013–01–11 Michael Elkins wrote: > > > On Fri, Jan 11, 2013 at 07:10:45PM +0100, Marco wrote: > > >>The problem is all the extra spaces you included in the macro > > >>string. > > > > > >I would never have thought of this! Still, I don't understand why it > > >only works with a non-empty mailbox. Either spaces are allowed and > > >it should work, or spaces are an error and mutt should yell at me. > > > > <space> is bound to view-message, so when the mailbox is not empty, > > it views the message, but you don't see it because the next command > > in the macro causes you to move back to the index. > > I remapped <space>, but still the same reasoning applies. That > explains it. > > > >Is this behaviour documented? Is there a better way to split the > > >command over several lines? IMO it makes it much easier to read. > > > > "When you press key in menu menu, Mutt will behave as if you had > > typed sequence." > > Reading this and understanding the consequences are two totally > different things :) > > > http://www.mutt.org/doc/devel/manual.html#macro > > > > There isn't really a good way to wrap long macros, other than > > breaking it up into several shorter macros and invoking them > > serially. > > I think the result will be ugly anyway, so I just have to put up the > fact that I have long line in my muttrc. > > Thanks for your help. > > Marco
Marco, it is unfortunate but I have found it's just easier to write all my macros in one line. When I use an editor to write or change them I open up a very wide terminal so vi(1) will make it easier for me to read them see any errors and spaces that shouldn't be there. I to this using tmux, which provides excellent ways, i.e. shortcuts to resize terminals and their layouts to accommodate this type of thing. -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
