From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.bugs Subject: bug#67393: 29.1; Slow to open file if autosave exists Date: Mon, 25 Dec 2023 18:40:08 +0000 Message-ID: <87le9im8hj.fsf@localhost> References: <83a5r5gdxk.fsf@gnu.org> <87frztc7iy.fsf@localhost> <867cl4kg4l.fsf@mail.linkov.net> <87cyuwdcb4.fsf@localhost> <868r5jse0m.fsf@mail.linkov.net> <83r0jbbg2z.fsf@gnu.org> <87mstz1l0b.fsf@localhost> <83bkafbdto.fsf@gnu.org> <87bkaf1iux.fsf@localhost> <83a5pzbbg7.fsf@gnu.org> <87zfxymdk6.fsf@localhost> <83jzp29q2v.fsf@gnu.org> <87tto6mc99.fsf@localhost> <83h6k69oec.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30034"; mail-complaints-to="usenet@ciao.gmane.io" Cc: materus213@gmail.com, 67393@debbugs.gnu.org, stefankangas@gmail.com, juri@linkov.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Dec 25 19:38:17 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 1rHpqC-0007Tx-Mq for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 Dec 2023 19:38:16 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rHppt-0003yZ-Kw; Mon, 25 Dec 2023 13:37:57 -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 1rHppr-0003yK-Rv for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 13:37:55 -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 1rHppr-0003VJ-Jj for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 13:37:55 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rHppy-0000ki-1O for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 13:38:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Ihor Radchenko Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 25 Dec 2023 18:38:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 67393 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 67393-submit@debbugs.gnu.org id=B67393.17035294392836 (code B ref 67393); Mon, 25 Dec 2023 18:38:02 +0000 Original-Received: (at 67393) by debbugs.gnu.org; 25 Dec 2023 18:37:19 +0000 Original-Received: from localhost ([127.0.0.1]:55374 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rHppH-0000jf-5e for submit@debbugs.gnu.org; Mon, 25 Dec 2023 13:37:19 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]:56197) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rHppC-0000jN-3B for 67393@debbugs.gnu.org; Mon, 25 Dec 2023 13:37:17 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id A7F63240104 for <67393@debbugs.gnu.org>; Mon, 25 Dec 2023 19:37:00 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1703529420; bh=xbzDCZDlJaH0UzMTrvw8M+J4EDb+QU3oJqOV6pNGNvA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=ZN0Q0/s5aO9WK0obPGOb146jMDtoITHxkZ0XkUoipH4Wbwjka2GnTXoGJu9GoJUzZ lBKjhR7qBEDdNfArETj4IPnnPmrmR5ec1LMFnD5JBrLzDhQt3hZ85FsUmmXQzXUpQP iZ1VvRKpB6C+sdHEXBkC6hmb8vCPjscbfQpllMnLU2Lul97JmGr+RuQuxYOdLC9nhE FCOJ7VGmRdc8+W2a0/yvP3lUyRXgOw13852eVEEBL4Msa//VvrplWEa1t2dY8Oi3/8 NpmpPV4H0xIBZIKt1h+kNGGC4F6j+witCIKzduJjn3k55vTOdT255+a9LpIn0a6q9S AYD/pDZ1jX7gw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4SzRT80Dycz9rxK; Mon, 25 Dec 2023 19:36:59 +0100 (CET) In-Reply-To: <83h6k69oec.fsf@gnu.org> 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:276882 Archived-At: Eli Zaretskii writes: >> I'd argue that messages that _must_ be acted, should not be messages. >> They should query user for action instead of blocking Emacs and not >> allowing to do anything other than C-g. > > You do realize that this is contrary to everything we currently do in > Emacs, right? We should the messages that must be acted upon > immediately, and use sit-for to make sure the user sees the message > and has an opportunity to act upon it. The message which started this > discussion was just like that: it informed the user that an autosave > file exists, so the user should consider using it. I disagree that sit-for gives an opportunity to act upon the message discussed in the bug report: "%s has auto save data; consider \\`M-x recover-this-file'". Consider that some command opens files one by one in sequence and one of these files has auto save data. `after-find-file' will pause that command, display the message, block Emacs (not allowing user to do anything), and then continue running the command. User has no chance to do anything about the auto save recovery until the command is finished and also has to wait extra few seconds while Emacs is blocked. (This is a real case I encountered with M-x org-agenda) In contrast, what I propose would make sure that the message is displayed for at least some period of time after the command finishes. Moreover, if multiple files have auto save data, messages about all these files will be displayed together without a need to dig into *Messages* buffer. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at