[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Iterative Tinkering depends on API stability
From: |
Tassilo Horn |
Subject: |
Re: Iterative Tinkering depends on API stability |
Date: |
Fri, 17 May 2024 09:37:06 +0200 |
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
> This also triggers when I use the W shortcut — though from the code I
> don’t understand why.
Oh, because there was a bug in the advice function which I didn't find
because I never use W. Here's a corrected version:
--8<---------------cut here---------------start------------->8---
;; I keep on sending replies (R) instead of wide replies (W), so
;; better make R ask if I'm really sure.
(defun th/mu4e-compose-reply-filter-args (args)
"Ask if we actually want a wide reply (Reply All)."
(list (or (car args) ;; the first arg is `wide'.
(yes-or-no-p "Wide reply? "))))
(advice-add #'mu4e-compose-reply
:filter-args
#'th/mu4e-compose-reply-filter-args)
--8<---------------cut here---------------end--------------->8---
> I shortened the question to y-or-n-p so I only have to type y.
I use (setq use-short-answers t) so that every yes-or-no-p becomes a
y-or-n-p.
Bye,
Tassilo