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: Thu, 28 Dec 2023 13:59:49 +0000 Message-ID: <875y0iwhpm.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> <87a5pym3zb.fsf@localhost> <83wmsz964m.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="30223"; 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 Thu Dec 28 14:57:14 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 1rIqss-0007dS-DO for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 28 Dec 2023 14:57:14 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rIqsk-0006Be-GG; Thu, 28 Dec 2023 08:57:06 -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 1rIqsh-0006B7-Dk for bug-gnu-emacs@gnu.org; Thu, 28 Dec 2023 08:57:03 -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 1rIqsh-0005zJ-5s for bug-gnu-emacs@gnu.org; Thu, 28 Dec 2023 08:57:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rIqsg-0006bi-ET for bug-gnu-emacs@gnu.org; Thu, 28 Dec 2023 08:57: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: Thu, 28 Dec 2023 13:57: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.170377180725375 (code B ref 67393); Thu, 28 Dec 2023 13:57:02 +0000 Original-Received: (at 67393) by debbugs.gnu.org; 28 Dec 2023 13:56:47 +0000 Original-Received: from localhost ([127.0.0.1]:38741 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rIqsQ-0006bD-R2 for submit@debbugs.gnu.org; Thu, 28 Dec 2023 08:56:47 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]:54013) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rIqsN-0006ax-G7 for 67393@debbugs.gnu.org; Thu, 28 Dec 2023 08:56:45 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 12DB224002B for <67393@debbugs.gnu.org>; Thu, 28 Dec 2023 14:56:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1703771798; bh=HxxbBuwLsu50gruaQn7jnsWRJmuEYsqEDIRHiyoqGXI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=ZAuhCxVR2CYlKu+CC8RTqAiHnJ9KOt2Owgd4d7AEvaoAFnhMHaCBZ/2JByQvTGeLA qAe5+Lf0MVDA8pPKYN18uvjIw5aYqVkDfF6weFGNaMQtheIQIJKlicBMvHPoy10WiF +IqUFum1+6I+0WbSWFiQkYuCOWyARNcFf00lifg4Jt0Tbm2pqYkUbCKiuww/sULmAz obxkxS+8zMxAi73/pVxAFbw9lu1YfwL7RJBR3CyDIUS2qL7BL0yuIFY8yyDVbjZpCs FQAzzfMUiY1lQYyEl3kRNAC/9ntdZMbPKiAhIdoBpqiWyP3DfOUHkXpgSsp5hWYQ2J EciqRr71wiOfQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4T196F2XSCz6tm4; Thu, 28 Dec 2023 14:56:37 +0100 (CET) In-Reply-To: <83wmsz964m.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:276976 Archived-At: Eli Zaretskii writes: >> > 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. It is actually what I had in mind, but I am concerned about several possible caveats: 1. Introducing a query where there was none previously may break noninteractive Emacs and existing code that makes an assumption about `find-file' not querying user in most cases. 2. autosave data is just one of several cases when `after-find-file' uses `sit-for': - "File exists, but cannot be read" - "Symbolic link that points to nonexistent file" - "%s has auto save data; consider \\`M-x recover-this-file'" - "File not found and directory write-protected" - "Use M-x make-directory RET RET to create the directory and its parents" It is not clear if all of these cases should ask user immediately and wait for an answer or just some of them. And if just some of them, whether to leave the `sit-for' delay after displaying message or not. >> 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. We are in agreement here. I also do not think that set-multi-message should be used everywhere. However, I do think that using `sit-for' to attract attention is not a good idea and such approach should be replaced either with explicit user prompt or, when the message is not as important, with something that does not block Emacs (like my proposal or something else we can come up with). -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at