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#59902: 30.0.50; Image overlay is not updated until the cursor moves to the overlay Date: Mon, 12 Dec 2022 08:35:43 +0000 Message-ID: <87pmcpc940.fsf@localhost> References: <87zgby87rm.fsf@localhost> <83h6y62kjp.fsf@gnu.org> <87ilim863y.fsf@localhost> <83lenh20fy.fsf@gnu.org> <87a63x7l1w.fsf@localhost> <83h6y51w66.fsf@gnu.org> <87wn6zr376.fsf@localhost> <83bkoby0zq.fsf@gnu.org> <87ilijfrac.fsf@localhost> <83o7sbwddn.fsf@gnu.org> <87zgbul2ln.fsf@localhost> <83bkoautll.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="33864"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 59902@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Dec 12 09:36:14 2022 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 1p4eIH-0008ZL-Rq for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 12 Dec 2022 09:36:13 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p4eIB-00033A-As; Mon, 12 Dec 2022 03:36:07 -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 1p4eI7-00032J-7Y for bug-gnu-emacs@gnu.org; Mon, 12 Dec 2022 03:36:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1p4eI6-0005Td-SE for bug-gnu-emacs@gnu.org; Mon, 12 Dec 2022 03:36:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p4eI6-0004kB-Ck for bug-gnu-emacs@gnu.org; Mon, 12 Dec 2022 03:36: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, 12 Dec 2022 08:36:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59902 X-GNU-PR-Package: emacs Original-Received: via spool by 59902-submit@debbugs.gnu.org id=B59902.167083415318225 (code B ref 59902); Mon, 12 Dec 2022 08:36:02 +0000 Original-Received: (at 59902) by debbugs.gnu.org; 12 Dec 2022 08:35:53 +0000 Original-Received: from localhost ([127.0.0.1]:51398 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p4eHx-0004jt-2q for submit@debbugs.gnu.org; Mon, 12 Dec 2022 03:35:53 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]:39831) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p4eHu-0004jj-Lw for 59902@debbugs.gnu.org; Mon, 12 Dec 2022 03:35:51 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id B99B8240103 for <59902@debbugs.gnu.org>; Mon, 12 Dec 2022 09:35:44 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1670834144; bh=/lebylAd5ZVxITEF1Cm8cthmvHEAcOop1aA/yCRMLok=; h=From:To:Cc:Subject:Date:From; b=c6mpl+AqW2eX5xofiLnyaG/vDCmNzqJRajLyaZ+W32aK+8jjYxqw9HRCzLo3bG3O3 LN0zLyvjgzais3R+GX5xYqc9Pgi7OT8QmrG82Jyg0MI79DjoTPqpJQ03a8SdHYqKUV nt3Mw6zJYr2AQst/NP4uOJGq82ndXB6mfIyFfsva4U4A2GJPv5UH0JPRtn0AAA8jMc 8mLshbBFJq/Mc/XRK5Iy5AS4il5qb1zFmh7097xQtIuSz1nd1uCn33znNv4jT1bat5 0DXeRQxr3ARGGXBt8BMDNGceH842ed5FQtb2NgSvi8X8dn0BnUXQMxj3kDJXQHvBp1 t2+USp5TEolnQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NVw1r023Qz9rxL; Mon, 12 Dec 2022 09:35:43 +0100 (CET) In-Reply-To: <83bkoautll.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:250685 Archived-At: Eli Zaretskii writes: >> No. Not really. Source block execution does not pass any information >> about updating/not updating images to Org image display code. Even if it >> did, the same issue could appear when the image file changes on disk >> outside Emacs. > > Then I don't think I understand what you expect Emacs to do in these > cases. We have no idea when the image file is replaced, and cannot > have such an idea without examining the file at high enough frequency. > Doing this "from time to time" is going to miss some changes, or take > note of them too late. What else is possible? For example, `create-image' could accept optional argument to update the cached image if the file modification time is newer than it was when the image was cached. >> Yet, do note that flickering two different image versions when moving >> point is unexpected even considering the information you provided. > > Flickering is expected when you do something that affects a large > portion of the Emacs display. For example, the same will happen if > you change a large overlay at high enough frequency. There's no way > around that except not doing that. Sorry, I used inaccurate word here. What I am referring to here is image overlay displayed old and new image when you move the cursor to the overlay and back repeatedly. > Why was this implementation chosen for whatever feature that produces > images? Emacs doesn't react instantly to changes in disk files that > it visits, and here you expect it to do so. Isn't it possible to > implement this in some other way, like have the program produce its > image data in a temporary Emacs buffer, then use that buffer's > contents for creating an image? Then I believe the updated image will > have a different hash value, and there will be no cache-related > collisions. It could be possible, but looks like unnecessary complication. Also, creating buffers often creates overheads associated with user hooks. I am not sure if something like (let ((revert-without-query '("."))) (with-current-buffer (find-file-noselect file) ;; Do not crown the buffer list. (unless (string-prefix-p " " (buffer-name)) (setf (buffer-name) (concat " " (buffer-name)))) (buffer-string))) is not going to cause significant slowdowns. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at