i wrote:
|So i have implemented two new hooks, *on-compose-enter* and
|*on-compose-leave*, which will set some variables so that at least
|a little bit of knowledge of the composed message is available,
|namely *compose-{from,sender,to,cc,bcc,subject}*.
|Note that `localopts' is by default enabled (now also for
Due to a faulty rebase (the code of [next] and [crawl] are located
in different files and have been rather heavily rewritten, so that
a git(1) --fixup or doesn't work) that didn't work due to the
missing one-line patch as follows, but now fixed.
diff --git a/lex.c b/lex.c
index 912209d..81caa46 100644
--- a/lex.c
+++ b/lex.c
@@ -787,8 +787,7 @@ commands(void)
interrupts = 0;
handlerstacktop = NULL;
- if (temporary_localopts_store != NULL) /* XXX intermediate hack */
- temporary_localopts_free(); /* XXX intermediate hack */
+ temporary_localopts_free(); /* XXX intermediate hack */
sreset((pstate & PS_SOURCING) != 0);
if (!(pstate & PS_SOURCING)) {
char *cp;
|`account's and the folder hooks), here meaning that settings will
|be reversed when the message has been sent.
Have fun, ciao.
--steffen
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
__________________________________
[email protected]
