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 20:17:28 +0000 Message-ID: <87a5pym3zb.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> <87le9im8hj.fsf@localhost> <83edfa9k1y.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="11604"; 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 21:15: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 1rHrLy-0002pf-4Y for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 Dec 2023 21:15:10 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rHrLk-0001Pg-U6; Mon, 25 Dec 2023 15:14:56 -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 1rHrLk-0001PY-2j for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 15:14:56 -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 1rHrLj-0001wG-R9 for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 15:14:55 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rHrLq-00028X-Ho for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 15:15: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 20:15: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.17035352718160 (code B ref 67393); Mon, 25 Dec 2023 20:15:02 +0000 Original-Received: (at 67393) by debbugs.gnu.org; 25 Dec 2023 20:14:31 +0000 Original-Received: from localhost ([127.0.0.1]:55433 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rHrLL-00027Y-7F for submit@debbugs.gnu.org; Mon, 25 Dec 2023 15:14:31 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]:37273) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rHrLI-00027H-U1 for 67393@debbugs.gnu.org; Mon, 25 Dec 2023 15:14:30 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 8C348240103 for <67393@debbugs.gnu.org>; Mon, 25 Dec 2023 21:14:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1703535256; bh=LXuxNznTBFGT/0ywOVbpDSp3lKttFJQT5RIb0J77Nq8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=X5JFPCMEGCvnMoHDxhGaTNyq0EOqEAiiIFUiNJ3LTjPPZgCWPpO8+evRGhfd8vEl1 Ybw9hl7KtCClA5BPsQDCcWUm1L3Cuj7Bn9/wmEA/wtCPXEjDA9etACPq4qryxBqCIy /h3DN7j7QBFxXjAbRd1Ku7RXKCQo/Hk/JUAG6+Zu8jBb5YMuUiDBk7aSCPs3yAZYiW p9y07+jLXhLHAaKabLRatgZA/8yhaKiPbUoBhobuALhKxTip59gyckrLmJbQvpZ3Hw vdLoYqGalKrZD2Ht+2fcI5zqR+qQZ6CdjiVNfAORzmYeSlprIRisAv74BmDBwWUNfP o0IAu6JhWe/0A== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4SzTdN0chzz6tw4; Mon, 25 Dec 2023 21:14:16 +0100 (CET) In-Reply-To: <83edfa9k1y.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:276890 Archived-At: Eli Zaretskii writes: >> 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) > > Such a command, if it existed, should perhaps provide a better > opportunity for the users, like prompt them for whether to recover > from each autosave file before continuing to the next one. May you please elaborate how a command calling of `find-file' or similar can provide such prompt? > But I was talking about "C-x C-f", the subject of this bug report, > where such a problem doesn't exist. By talking about a different > command you simply change the subject, which doesn't help to make the > discussion constructive. Fair. My reply was more to (when (and warn msg) (message "%s" msg) (or not-serious (sit-for 1 t)))) ^^^^^^^^^^^^^ rather than to the original bug report. But I am not sure if it is worth it to open a brand-new bug report about `find-file' used from complex commands. >> In contrast, what I propose would make sure that the message is >> displayed for at least some period of time after the command finishes. > > Imagine a command that needs the user to respond within a short time > interval, after which the message becomes irrelevant, because the > situation changed in a way that the information there is not longer > pertinent. Like in those mythical Mission Impossible movies: this > message will auto-destruct in 5 seconds. How will leaving all of > those message on display help in that case? I consider such situation worth a full interactive prompt, not limited to 5 seconds. For example, C-x C-f could prompt about recovering from backup file, if such file is detected. >> 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. > > "Dig into *Messages*" is a strange phrase to hear from a veteran Emacs > user. I'd expect looking in *Messages* to be your second nature. It is not. > Some users even have the habit of leaving *Messages* constantly on > display -- there's your "leave messages on display" proposal already > available if someone wants that. After `set-multi-message' became a thing, I no longer need to consult *Messages* often. `set-multi-message' was really an eye-opener on how much useful information I miss when messages are coming in quick succession. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at