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: Mon, 25 Dec 2023 21:08:41 +0200 Message-ID: <83edfa9k1y.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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15777"; 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 Mon Dec 25 20:09:13 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 1rHqK9-0003rD-7K for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 Dec 2023 20:09:13 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rHqJv-0000GB-1s; Mon, 25 Dec 2023 14:08:59 -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 1rHqJs-0000Fd-H6 for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 14:08: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 1rHqJs-0000Ev-8u for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 14:08:56 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rHqJy-0006tB-HI for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 14:09: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, 25 Dec 2023 19:09: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.170353134026473 (code B ref 67393); Mon, 25 Dec 2023 19:09:02 +0000 Original-Received: (at 67393) by debbugs.gnu.org; 25 Dec 2023 19:09:00 +0000 Original-Received: from localhost ([127.0.0.1]:55395 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rHqJw-0006sv-C2 for submit@debbugs.gnu.org; Mon, 25 Dec 2023 14:09:00 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40150) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rHqJt-0006sg-Q9 for 67393@debbugs.gnu.org; Mon, 25 Dec 2023 14:08:58 -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 1rHqJg-0000Dw-VN; Mon, 25 Dec 2023 14:08:44 -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=1ayfc2b4FpgMfL3QKKqTz7ogrJ2zd7YL8tToEy7IE1s=; b=j3MFgKcMNmUj orFf00sicBcdCLzU6aDeexgztkVm+4RPTBcnzITeWc+d6I1ar69N8OtaRHVwdDpiTsQSkCShYUjIW Lj4Im7vWqX4AdmFjoEVpG9AViXneZ4GM3IadoTMJ13EvOu8+TD8QM8omBPOpNW/IPK7CRdyfRjx1a jqhuzqR3xv2BWz32IslCx5kzkE/Lu1q9iRNUulQEaAqU6Mx9CeLt88/pOAYyq+Fp9gwfvvK7ALO3F me4cJVnZOquuFmrjZW3Pl+BXeHs11KD2ctZt/N2kaTqPKQCckxBa8M+Vp69359zS6CczijrnUUiK1 Beh4Gla1vpBYpaIEM4GR1A==; In-Reply-To: <87le9im8hj.fsf@localhost> (message from Ihor Radchenko on Mon, 25 Dec 2023 18:40:08 +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:276885 Archived-At: > From: Ihor Radchenko > Cc: juri@linkov.net, stefankangas@gmail.com, materus213@gmail.com, > 67393@debbugs.gnu.org > Date: Mon, 25 Dec 2023 18:40:08 +0000 > > Eli Zaretskii writes: > > > 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) 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. 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. > 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? > 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. 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.