From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#63311: 30.0.50; [PATCH] smtpmail-send-it split Date: Mon, 06 Nov 2023 18:57:59 +0100 Message-ID: <87pm0mepco.fsf@ledu-giraud.fr> References: <87jzxmsyyr.fsf@ledu-giraud.fr> <83pm763y3r.fsf@gnu.org> <87h6si5aor.fsf@ledu-giraud.fr> <83a5ya3u16.fsf@gnu.org> <871qjm56ej.fsf@ledu-giraud.fr> <87r0l9ejmm.fsf@ledu-giraud.fr> <834ji5aatw.fsf@gnu.org> <87bkcde4bz.fsf@ledu-giraud.fr> <83r0l98e6w.fsf@gnu.org> <87lebhckp2.fsf@ledu-giraud.fr> <83msvw904n.fsf@gnu.org> <87wmv0zb6v.fsf@ledu-giraud.fr> <8334xo8khh.fsf@gnu.org> <87ttq0nuq5.fsf@ledu-giraud.fr> <835y2g42zj.fsf@gnu.org> <87msvsfacs.fsf@ledu-giraud.fr> <834ji041jj.fsf@gnu.org> <87zfzrfaho.fsf@ledu-giraud.fr> <83msvr2gy3.fsf@gnu.org> <87jzqux4cu.fsf@ledu-giraud.fr> <83fs1i3kxy.fsf@gnu.org> Reply-To: Manuel Giraud Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35429"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 63311@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Nov 06 18:59:10 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1r03sT-00090v-FY for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Nov 2023 18:59:09 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r03rt-0001PK-Mz; Mon, 06 Nov 2023 12:58:33 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r03rm-0001Or-JR for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2023 12:58:27 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1r03rk-0000ob-PX for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2023 12:58:25 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1r03sL-0006iB-U8 for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2023 12:59:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Manuel Giraud Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Nov 2023 17:59:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63311 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 63311-submit@debbugs.gnu.org id=B63311.169929352425760 (code B ref 63311); Mon, 06 Nov 2023 17:59:01 +0000 Original-Received: (at 63311) by debbugs.gnu.org; 6 Nov 2023 17:58:44 +0000 Original-Received: from localhost ([127.0.0.1]:40677 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1r03s3-0006hQ-JQ for submit@debbugs.gnu.org; Mon, 06 Nov 2023 12:58:43 -0500 Original-Received: from ledu-giraud.fr ([51.159.28.247]:39117) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1r03s0-0006hE-9p for 63311@debbugs.gnu.org; Mon, 06 Nov 2023 12:58:41 -0500 DKIM-Signature: v=1; a=ed25519-sha256; c=simple/simple; s=ed25519; bh=xtNDuPoN ZE6l602RPj+fFyjMuqAoOm+f1u/Wtsi1MDE=; h=date:references:in-reply-to: subject:cc:to:from; d=ledu-giraud.fr; b=ATDrLWo/3vgQPSFBtndrbVFz/8mWN9 rUj2BLsdJ0Wf9XKCNOa2GqbFPewGtnaQo+HTRhx3AC8ts5wcnvlZkUAA== DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; s=rsa; bh=xtNDuPoNZE6l602R Pj+fFyjMuqAoOm+f1u/Wtsi1MDE=; h=date:references:in-reply-to:subject: cc:to:from; d=ledu-giraud.fr; b=fSmdkSbbd7DgYT56PXIOemuJ7XFhfXh+j5gEgh d6xbhj9YC6cPSskvR6DEhMLTXfWJFR+vyVlQGr2DIZoVNcTZDcOlPrqMRXtxUDyvBl9Ylf to5x730S1+j9geWm5vHIjPHxc4qBVLHNjC7aYd3VvaSot+qjQr3438O5Z4MdgkjM3Ym+tO 1QTGDn/NMzg99xHMOLBWaucQufnUBdAUJEZxxMMHW5WIwJuD6bM2k9x56aUQgiQHk2bPAT qpPxV6IbeVc0ljIL+x9xhJeeSOGWK+jfwvcCzaA84jph/BQYpmnqCnoF/+ID0R3kqAevaK nmEBqy+L5Mb6OUeWkvKWeXrw== Original-Received: from computer ( [10.1.1.1]) by ledu-giraud.fr (OpenSMTPD) with ESMTPSA id c9c1273d (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 6 Nov 2023 18:58:01 +0100 (CET) In-Reply-To: <83fs1i3kxy.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 Nov 2023 18:28:41 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:273891 Archived-At: Eli Zaretskii writes: >> From: Manuel Giraud >> Cc: 63311@debbugs.gnu.org >> Date: Mon, 06 Nov 2023 16:56:33 +0100 >> >> Eli Zaretskii writes: >> >> >> Yes but how would I do that. My idea was to left much code unmodified >> >> (with all 'error' calls in case something goes wrong). But how the >> >> 'main-thread' could fetch these errors. >> > >> > Using thread-last-error, or at least that's what I had in mind. >> >> It seems that 'thread-last-error' is global for all threads of Emacs so >> I don't it would work. Doesn't a thread record its error status and >> message? > > Sorry, I don't understand what exactly you are asking and what you are > saying. > > Yes, thread-last-error accesses a global storage, but I fail to see > how this is a problem: if the main thread fetches the error in a > timely fashion, it should still work. And if, for some reason, this > is not good enough, we could come up with a more fine-grained > mechanism. But first I'd like to see a description of a real problem > with the existing mechanism: after all, it isn't expected that every > single thread you launch will die due to an error, right? So the > situation where a thread dies and we need to access its error should > be relatively rare, and a global resource could still be adequate. So just for recap, the idea is to have a command ('message-send-asynchronously' as you suggested) that will just be wrapper around 'message-send' and creates a thread to send the current buffer. Such a thread could be stored in a list and, by mean of a timer, the main-thread would sometimes look if this thread is dead. 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? Or worse: the thread is dead, (thread-last-error) returns nil... but it was cleared from another part of Emacs. -- Manuel Giraud