Vincent Lefevre wrote: > On 2015-08-21 13:21:56 +0200, Vincent Lefevre wrote: > > On 2015-08-21 13:05:39 +0200, Vincent Lefevre wrote: > > > On 2015-08-20 19:53:36 -0700, Kevin J. McCarthy wrote: > > > > Vincent Lefevre wrote: > > > > > In "<save-message>=INBOX.Trash<enter>", the "=INBOX.Trash" will be > > > > > saved to the history, and it is not possible to temporarily disable > > > > > the history (e.g. for such macros). So, indeed, this would be very > > > > > annoying. > > > > > > > > I believe adding a leading space will keep it from being added to > > > > history: > > > > "<save-message> =INBOX.Trash<enter>" > > > > > > No, this doesn't work as expected for mailboxes and patterns: the > > > space (and the following text) is appended to the last entry. > > > > I've found a workaround. For my limit-to-all macro: > > > > macro index \CA "<limit>~<backspace> ~A\r" "limit to all" > > Unfortunately, this trick doesn't work with <save-message>. > First, the space will trigger <buffy-cycle> with the default > key binding. One can avoid that by using <quote-char> before > the space, like: > > "<save-message>=<backspace><quote-char> =INBOX.Trash" > > but though one now has a leaning space character, this doesn't > work because the = character is no longer regarded as a mailbox > shortcut. One would need to avoid mailbox shortcuts, which may > not be a big problem for macros.
Doh... I should have known better, having just wrote thre error checking for regexp vs mailbox shortcut handling in hooks. Sorry to waste your time with a bad suggestion! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA http://www.8t8.us/configs/gpg-key-transition-statement.txt
signature.asc
Description: PGP signature
