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#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld" Date: Tue, 31 Dec 2024 21:54:02 +0200 Message-ID: <86v7uzljc5.fsf@gnu.org> References: <878qrxgg74.fsf@Phoenix> <864j2lnf1j.fsf@gnu.org> <87ldvvhhqo.fsf@localhost> <87frm3elkr.fsf@Phoenix> <878qrvhe0k.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14783"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 75209@debbugs.gnu.org, njackson@posteo.net To: Ihor Radchenko Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Dec 31 20:57:23 2024 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 1tSiMk-0003f9-RF for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 31 Dec 2024 20:57:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSiMX-0005vp-Up; Tue, 31 Dec 2024 14:57:12 -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 1tSiMQ-0005uz-3p for bug-gnu-emacs@gnu.org; Tue, 31 Dec 2024 14:57:02 -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 1tSiMP-0003s7-SE for bug-gnu-emacs@gnu.org; Tue, 31 Dec 2024 14:57:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=References:In-Reply-To:From:Date:To:Subject; bh=h8nxw/i796oJGrPXZiB5NXM+L6KdNJZk3W50mlX3A60=; b=NBYuA0Oda+9YU0bzyI88a3VNq0HKi2iCV02iHpto/sV/otop8BD6hHCkTEPYC+k8cEBZGqHyeFKNGBtf/rH6DcwDfkCQ0Uf/rvAKShsYLQagmdgjVqo4OEn1PUR3tRmxnDNXervhC/G3WM9A2CNpr2lUm/hpRn9yAtP+dPx2k3s4eUI2i76OyGCUZB73q60ivRwg04qZM++J4wBoBEpcrkvSCf0MMLen6gCczxBdjGXGhvPGkFvdJyQzRNngJWIfrbwB0CcapvRZvUZAsDlDrh3S26V3GAwBC5E6dtfrvkQwFnbZT/2oCn2IDXgEkhadGAK23ffKwLBtqievU/Jwwg==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tSiMP-0005eF-ML for bug-gnu-emacs@gnu.org; Tue, 31 Dec 2024 14:57:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 31 Dec 2024 19:57:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 75209 X-GNU-PR-Package: emacs Original-Received: via spool by 75209-submit@debbugs.gnu.org id=B75209.173567498621643 (code B ref 75209); Tue, 31 Dec 2024 19:57:01 +0000 Original-Received: (at 75209) by debbugs.gnu.org; 31 Dec 2024 19:56:26 +0000 Original-Received: from localhost ([127.0.0.1]:36874 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tSiLp-0005cz-S2 for submit@debbugs.gnu.org; Tue, 31 Dec 2024 14:56:26 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:57786) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tSiLn-0005cc-OB for 75209@debbugs.gnu.org; Tue, 31 Dec 2024 14:56:24 -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 1tSiJa-0002zf-4u; Tue, 31 Dec 2024 14:54:06 -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=h8nxw/i796oJGrPXZiB5NXM+L6KdNJZk3W50mlX3A60=; b=XD8Ah+fj1UOO lztOJhtG0awD+W5+IscbVX7YV93ytE6OPqFqfSFVPliXpPOcTgdvtiRy4nTqI5fzK2HR2mAIzUBlD 6kdbiDfshJL4/w9gXDMlhNnbawfQjsrFjKMkMdst2jCpNYJbfmtVwK7MIPArAoELFluDtNYdhRxDQ tRrA9Jp6Ugj1/LOvNI3DJJe0uNoW0p4DjR5C/vbZ4HMRcMCzE0emSJjopYeJIvEmpAvZYxh53YuOx cPATaJSzPGrALMxsZlM9TcZjcOKpzlwIo3wIP7kcMz7q+B7guAdOaVc0AhK+WQ+RmIdsxC6yt34ms b9cvXJuL70IM/ZrAy5k4Fw==; In-Reply-To: <878qrvhe0k.fsf@localhost> (message from Ihor Radchenko on Tue, 31 Dec 2024 19:02:35 +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:298053 Archived-At: > From: Ihor Radchenko > Cc: Eli Zaretskii , 75209@debbugs.gnu.org > Date: Tue, 31 Dec 2024 19:02:35 +0000 > > "N. Jackson" writes: > > >> Or, alternatively, C-g in the middle of writing. > > > > I use C-g very frequently. I type `M-x' and then realise I want to > > do `C-h f' first instead, so I do `C-g' to exit from the M-x prompt. > > Or I do an isearch and then change my mind (or find and read > > whatever I was looking for) then I do `C-g' (twice, I think) to exit > > the isearch and get back to where I started. Usages like that. > > From my (probably naive) point of view, if that messes up Org Mode, > > then Org Mode is doing something wrong. > > That should not be a problem then. > Reading/writing GC file is done using timer and, AFAIK, Emacs should not > run timers while you are running a command. If this happens while the user types some command, then timers could fire during that typing, since people rarely type fast enough to not let timers run. But all this is not relevant, because Emacs binds inhibit-quit to a non-nil value while it runs the timer function. So, unless the timer in question somehow forcibly resets inhibit-quit to nil, C-g should not be able to interrupt a timer. > >> gc-lock.eld is a file used to flag that cache dir is being worked > >> on by multiple emacs instances. GC here refers to > >> garbage-collecting cache data. > > > > I do run multiple (two) instances of Emacs. One is my normal > > session where I use Org quite heavily. The other is my Gnus session > > in which I never open an Org file and never (as far as I know) use > > any Org features. > > Gnus may load Org. (AFAIU, it does it when viewing gnus articles) > > Another possible scenario is two Org instances writing to the same file > at the same time. > If it is what is happening in your case, your problem may be similar to > https://list.orgmode.org/orgmode/CAMJKaZxA_VmLdFP_u1rNiF2s0X2kVivjT31jEM_r3BYCHri1PQ@mail.gmail.com/ Can't Org prevent more than one session writing to this file? We have file locks which can be used here, I think.