From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#63311: 30.0.50; [PATCH] smtpmail-send-it split Date: Mon, 06 Nov 2023 21:21:21 +0200 Message-ID: <838r7a3cy6.fsf@gnu.org> 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> <87pm0mepco.fsf@ledu-giraud.fr> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26364"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63311@debbugs.gnu.org To: Manuel Giraud Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Nov 06 20:22:46 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 1r05BN-0006de-TR for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Nov 2023 20:22:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r05B4-0007zT-J1; Mon, 06 Nov 2023 14:22:26 -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 1r05B3-0007z5-5V for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2023 14:22:25 -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 1r05B2-0006vy-U3 for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2023 14:22:24 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1r05Be-0000Ls-3u for bug-gnu-emacs@gnu.org; Mon, 06 Nov 2023 14:23:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Nov 2023 19:23:02 +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.16992985421299 (code B ref 63311); Mon, 06 Nov 2023 19:23:02 +0000 Original-Received: (at 63311) by debbugs.gnu.org; 6 Nov 2023 19:22:22 +0000 Original-Received: from localhost ([127.0.0.1]:40711 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1r05B0-0000Ks-9i for submit@debbugs.gnu.org; Mon, 06 Nov 2023 14:22:22 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51530) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1r05Ay-0000Kf-Co for 63311@debbugs.gnu.org; Mon, 06 Nov 2023 14:22:21 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r05AH-0006o9-0u; Mon, 06 Nov 2023 14:21:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=pMz3j3LIYyYIue3zi1yNm4AMD0bU0TelKHbIphEcBi4=; b=akHfzqtEUhQh QJZbZpeJqCvmmdjCmT0AGQVg6jnrf9eIuZ6dwFYASMBRNI14qMpm7mEMka7HugoVGwnvUdiUBVpId lpYRHbvo8mLnzE0f52626x9XSHAlNzTFi2w2gldwX+L+4btmtzG1YjACVxBT8nohUJ5iqVymZ9hWn zPGv30V+iYfbuAIBQK1CWVt9RWtwed6xRcfo+3F/vE+o9ow7n0dWqEnh0U7KZSkaTDxPSsvB8gEw2 qIfXdM64fm23Cumy/x8jLE2fnM08XZUfBlzk1jrK6qxRC2/vTFyrvx4thBqIY2LqEJ9f4cf80yDKz uCyMRt/PQzAEJGTq7c+Piw==; In-Reply-To: <87pm0mepco.fsf@ledu-giraud.fr> (message from Manuel Giraud on Mon, 06 Nov 2023 18:57:59 +0100) 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:273893 Archived-At: > From: Manuel Giraud > Cc: 63311@debbugs.gnu.org > Date: Mon, 06 Nov 2023 18:57:59 +0100 > > 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. Something like that, yes. > 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. > 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.