At Wed, 14 Apr 2010 09:15:55 +0200, Vitaly Mayatskikh wrote: > Quick hack: > > --- wl/wl-mime.el 4 Jan 2010 09:39:12 -0000 1.110 > +++ wl/wl-mime.el 14 Apr 2010 07:15:27 -0000 > @@ -925,11 +925,12 @@ With ARG, ask destination folder." > (method . wl-mime-decrypt-application/pgp-encrypted) > (major-mode . wl-original-message-mode))) > > - (ctree-set-calist-strictly > - 'mime-acting-condition > - '((mode . "extract") > - (major-mode . wl-original-message-mode) > - (method . wl-mime-save-content))) > + ;; (ctree-set-calist-strictly > + ;; 'mime-acting-condition > + ;; '((mode . "extract") > + ;; (major-mode . wl-original-message-mode) > + ;; (method . wl-mime-save-content))) > + > (set-alist 'mime-preview-following-method-alist > 'wl-original-message-mode > (function wl-message-follow-current-entity)) Thanks for this tip, Vitaly. I presume this would disable wl-mime-save-content entirely? I examined the differences between wl-mime-save-content and it is very close to mime-save-content; it just seems to have a few extra filename tricks. I wonder if, going forward, loading WL could remove mime-save-content in mime-acting-condition and use wl-mime-save-content instead. This would eliminate some confusion, I think. Unfortunately I see no ctree-* method for removing an ‘acting condition’, and, not understanding the condition-tree format, I do not feel comfortable writing one now. best, Erik
Attachment:
pgp6BDrCzBLso.pgp
Description: PGP signature