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#67393: 29.1; Slow to open file if autosave exists Date: Wed, 27 Dec 2023 14:34:01 +0200 Message-ID: <83wmsz964m.fsf@gnu.org> 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> <87a5pym3zb.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18450"; mail-complaints-to="usenet@ciao.gmane.io" Cc: materus213@gmail.com, 67393@debbugs.gnu.org, stefankangas@gmail.com, juri@linkov.net To: Ihor Radchenko Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Dec 27 13:35: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 1rIT81-0004YC-CW for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 27 Dec 2023 13:35:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rIT7p-0005vB-Jz; Wed, 27 Dec 2023 07:35:05 -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 1rIT7o-0005v2-7P for bug-gnu-emacs@gnu.org; Wed, 27 Dec 2023 07:35:04 -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 1rIT7n-0000TL-UB for bug-gnu-emacs@gnu.org; Wed, 27 Dec 2023 07:35:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rIT7m-0004g3-G5 for bug-gnu-emacs@gnu.org; Wed, 27 Dec 2023 07:35: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: Wed, 27 Dec 2023 12:35: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.170368046817928 (code B ref 67393); Wed, 27 Dec 2023 12:35:02 +0000 Original-Received: (at 67393) by debbugs.gnu.org; 27 Dec 2023 12:34:28 +0000 Original-Received: from localhost ([127.0.0.1]:35477 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rIT7E-0004f5-7A for submit@debbugs.gnu.org; Wed, 27 Dec 2023 07:34:28 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35678) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rIT7B-0004er-BF for 67393@debbugs.gnu.org; Wed, 27 Dec 2023 07:34:26 -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 1rIT75-0000F3-4D; Wed, 27 Dec 2023 07:34:19 -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=SApVzia/Z618dudE/vjCxOjgqMY7KX3CdkV1vBPHc2M=; b=rJ6PRvHqrQ97 22aVu456/7J76fCH50g4jq2yVWKqNQraRuSrF7qnb7SdH/FQJvUBJWukZeaMbD7cIxo3CrPnsHV3V GdMOb3J3BLZ3d7jdjaOuns6GgATAvpB9Ux8nIlZXl+Kv7mz3k8f+pFPkp4fRwkvUbuTbtgy1j2QQx IfPnBvZEb9+D03PxBTm7vcZOibBoFsk9hc+RNoW5rQG7+PcC9FEicBS4ujjBlt9i8a/3ypcVETL3D 2PFKBMtp5drElbvG9Tly7U2Bi1u1RydpwDkoS7fbWHDkErACLSaee/VJNuN3gq4P6pndSdkcBxNJh Q8Ga58dbgwYGtaDzekqA8Q==; In-Reply-To: <87a5pym3zb.fsf@localhost> (message from Ihor Radchenko on Mon, 25 Dec 2023 20:17:28 +0000) 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:276933 Archived-At: > From: Ihor Radchenko > Cc: juri@linkov.net, stefankangas@gmail.com, materus213@gmail.com, > 67393@debbugs.gnu.org > Date: Mon, 25 Dec 2023 20:17:28 +0000 > > 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? I'm not sure I understand what you mean, because the answer seems too obvious: just prompt after opening each file that has autosave data. But that's probably not what you had in mind. > >> 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. Yes. My point being that just a fire-and-forget message is not good in these cases anyway, so the issue we are discussing doesn't have to cater to such cases. > >> 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. To each their own. I think set-multi-message has its uses, but I don't think it can solve all of the cases, in particular those where we need to attract the users' attention to a particularly important message.