* Jon LaBadie <[email protected]> [09-21-15 17:27]: > On Mon, Sep 21, 2015 at 02:36:34PM -0400, Ben Boeckel wrote: > > On Mon, Sep 21, 2015 at 12:32:02 -0500, David Champion wrote: > > > set my_wait_key=$wait_key > > > unset wait_key > > > set wait_key=$my_wait_key > > > > Well, that looks nasty, but it works: > > > > macro generic \Cy \ > > ":set my_wait_key = $wait_key<return>:unset > > wait_key<return><shell-escape>killall -USR1 offlineimap<enter>:set wait_key > > = $my_wait_key<return>:unset my_wait_key<return>" \ > > "kick offlineimap" > > > > I still think some command or function to do this would help a lot. > > Wrapping all functions like this is…tedious to say the least. It also > > makes reading these things annoying since the meat of the binding is > > buried 65 characters into the line. > > Can a macro be executed by another macro? > Back in my troff days we used to write macros like > "save_a_group_of_settings" and "restore_saved_settings". > > After the housekeeping macro calls appeared at the start > and end of several other definitions, the mind learns to > ignore them when considering the logic of the macro later.
I call one macro from another, but I assign the called micro to a key combination and call it via the key combination. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net
