[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63311: 30.0.50; [PATCH] smtpmail-send-it split
From: |
Manuel Giraud |
Subject: |
bug#63311: 30.0.50; [PATCH] smtpmail-send-it split |
Date: |
Tue, 07 Nov 2023 10:06:58 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Manuel Giraud <manuel@ledu-giraud.fr>
>> Cc: 63311@debbugs.gnu.org
>> Date: Mon, 06 Nov 2023 21:55:49 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> If it is dead and (thread-last-error) returns nil maybe we can conclude
>> >> that everything went well. But if (thread-last-error) returns a
>> >> message, it could be message from any other Emacs thread: what to do in
>> >> such case?
>> >
>> > Display a message about the error.
>>
>> I mean, the last error message could come from another thread not
>> related in anyway to mail sending. No?
>
> It could, but why would there be other threads in this case?
It seems that threads aren't used much in Emacs but isn't it dangerous
to consider we're the only one using them? I don't if it would be easy
but I think that it would be good to have a function like this:
(thread-error thread)
that would return the error message of the given thread like the global
'thread-last-error' does.
>> >> Or worse: the thread is dead, (thread-last-error) returns
>> >> nil... but it was cleared from another part of Emacs.
>> >
>> > This means it exited successfully. We could also maintain a data
>> > structure where successfully-exiting threads will leave their success
>> > status together with some id of the message they sent -- unlike a
>> > thread that dies abruptly due to an error, a successful thread can
>> > store the information in the data structure before exiting.
>>
>> Yes why not but then I'd have to modify internals of 'message-send':
>> something I thought I could escape.
>
> I thought we were talking about a new function for this purpose, which
> would replace message-send, no? Then that new function could have
> this code.
You're right it should be feasible inside this new function with
something like that:
--8<---------------cut here---------------start------------->8---
(make-thread #'(lambda ()
(if (message-send)
(store-my-success)
(store-my-failure))))
--8<---------------cut here---------------end--------------->8---
and then the main-thread will read those success or failure and act
accordingly.
--
Manuel Giraud
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, (continued)
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Manuel Giraud, 2023/11/05
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/05
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Manuel Giraud, 2023/11/06
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/06
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Manuel Giraud, 2023/11/06
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/06
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Manuel Giraud, 2023/11/06
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/06
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Manuel Giraud, 2023/11/06
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/06
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split,
Manuel Giraud <=
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/07
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Manuel Giraud, 2023/11/07
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/07
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Richard Stallman, 2023/11/02
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/03
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Manuel Giraud, 2023/11/03
- bug#63311: 30.0.50; [PATCH] smtpmail-send-it split, Eli Zaretskii, 2023/11/03