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 17:18:42 +0000 Message-ID: <87tto6mc99.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2212"; 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 18:16:34 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 1rHoZ8-0000Pg-9p for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 Dec 2023 18:16:34 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rHoYY-00084f-I6; Mon, 25 Dec 2023 12:15:58 -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 1rHoYW-00084Q-EB for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 12:15: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 1rHoYW-0006v0-5O for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 12:15:56 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rHoYc-0001s0-GA for bug-gnu-emacs@gnu.org; Mon, 25 Dec 2023 12:16: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 17:16: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.17035245485671 (code B ref 67393); Mon, 25 Dec 2023 17:16:02 +0000 Original-Received: (at 67393) by debbugs.gnu.org; 25 Dec 2023 17:15:48 +0000 Original-Received: from localhost ([127.0.0.1]:55247 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rHoYN-0001SF-MV for submit@debbugs.gnu.org; Mon, 25 Dec 2023 12:15:48 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]:45533) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rHoYJ-00018g-0x for 67393@debbugs.gnu.org; Mon, 25 Dec 2023 12:15:45 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 48076240104 for <67393@debbugs.gnu.org>; Mon, 25 Dec 2023 18:15:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1703524530; bh=PI8rXjdL2W8F6nBxqTBwj0jsVnwzNQB60udNelb+j9w=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=PGTbzcEu2z6Ze8W+fN2624hDrf9ZdgUeFi5xV8xJgTYmuO6JST0WpxcWfbZUe27UX ++1jOLn1X8A1t4CAeFjXNjmrB1BFkjeQChwaqErYWfpIammll/gOynMk7tnJcxH+ay 4bp5sSa/OK9gXQ8e/Ls1vbRfL/Dp7gtYPwFlKzFcpPKSSxboiYNQLEFM75yXVJyeu8 uwHhvBDn9+nme5aDEtv4rbi+pmFu1B/qLFyRfvi9qn3QCt1P5EGQIW9//wrL658lur z2AoTjkOQ4PUe+c7jf3M+VwHelQcPkTvLC3WvKU730U2mQl0zTiv9IK6jMFDJJhplu KQ6ihyx+4pSQQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4SzPg558nRz9rxD; Mon, 25 Dec 2023 18:15:29 +0100 (CET) In-Reply-To: <83jzp29q2v.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:276876 Archived-At: Eli Zaretskii writes: >> For example, the message "File exists, but cannot be read" from >> `after-find-file' may be written as >> >> "Opening file: exists, but cannot be read" > > Sorry, but I don't see how this would help. "Opening file" could > allude to anything; Emacs opens a lot of files all the time. A > delayed message will run a high risk of missing its point, unless it > presents a lot of relevant context, as a minimum the command which > caused it with that command's arguments. Do note that I am not proposing to delay the message. It will be displayed immediately; just will not block. As for missing the point, the point is either current command opening a file - then, the context is clear; or a complex command doing many things, including opening a file - then, I doubt that blocking is very helpful. > And having said that, I'm not sure this is a good idea even if we > present enough context. For starters, many messages must be acted > upon immediately. 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. >> > Again: how will this look in practice, including the dismissal action? >> >> Try the following proof-of-concept code: > > Thanks, but this would mean a complete redesign of the Emacs messaging > UI. This kind of display no longer fits the mini-window paradigm we > are using, it will need a separate large enough window for showing > series of messages (in which case we don't need to much wizardry to > scroll through them and selectively delete them). Do we really want > to make such drastic changes in our UI? I believe that such changes would be helpful. Apart from addressing the problem here, they might be useful to address the concerns about messages displayed by Elisp threads, timers, and async process callbacks. Also, if we ever get true multithreading, some way to display and separate messages coming simultaneously would be a good thing to have. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at