On Mar 08, 2025, at 03:34-0500 "Dirk-Jan C. Binnema" <
dj...@djcbsoftware.nl> wrote:
> Hi Kourosh,
>
> On Wednesday Mar 05 2025, Kourosh Kalayeh wrote:
>
>> On Mar 31, 2024, at 12:07-0400 "Dirk-Jan C. Binnema" <
dj...@djcbsoftware.nl> wrote:
>
> <snip>
>
>> I followed your suggestion to use mu4e-compose-type, but it seems this variable is always nil when evaluated in the function assigned to message-signature. Specifically, my debug message shows:
>>
>> DEBUG: kk-mu4e-signature called with mu4e-compose-type = nil
>>
>> Here's the minimal example of my function:
>>
>> (defun kk-mu4e-signature ()
>> "Insert signature only for new messages."
>> (message "DEBUG: kk-mu4e-signature called with mu4e-compose-type = %s"
>> mu4e-compose-type)
>> (if (eq mu4e-compose-type 'new)
>> "My Signature"
>> nil))
>>
>> Is there a recommended way to ensure mu4e-compose-type is available
>> when message-signature is evaluated? Am I missing something?
>
> It worked for reply/forward/.. but not for new (probably after the
> compose rework). Anyway, pushed a fix, thanks!
>