bug#66993: closed ([PATCH] project.el: avoid asking user about project-list-file lock)

[GNU bug Tracking System]

Your message dated Wed, 15 Nov 2023 15:38:20 +0200
with message-id <83r0krqgqb.fsf@gnu.org>
and subject line Re: bug#66993: [PATCH] project.el: avoid asking user about 
project-list-file lock
has caused the debbugs.gnu.org bug report #66993,
regarding [PATCH] project.el: avoid asking user about project-list-file lock
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
66993: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66993
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [PATCH] project.el: avoid asking user about project-list-file lock Date: Tue, 07 Nov 2023 16:28:04 -0500

Tags: patch


This fixes a periodic issue that happens with multiple Emacs instances
and project.el.

Maybe this isn't the right way to change the behavior of
ask-user-about-lock though; possibly we should add some new defcustom to
customize it.  Happy to do that if that's preferred.


In GNU Emacs 29.1.50 (build 15, x86_64-pc-linux-gnu, X toolkit, cairo
 version 1.15.12, Xaw scroll bars) of 2023-10-25 built on
 igm-qws-u22796a
Repository revision: 5cbca757f620c7b4ca31776711a247b8f266c36e
Repository branch: emacs-29
Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
System Description: Rocky Linux 8.8 (Green Obsidian)

Configured using:
 'configure --config-cache --with-x-toolkit=lucid
 --with-gif=ifavailable'

0001-project.el-avoid-asking-user-about-project-list-file.patch
Description: Text Data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#66993: [PATCH] project.el: avoid asking user about project-list-file lock
>
>
>
>
> Date: 
>
> Wed, 15 Nov 2023 15:38:20 +0200
>
>
>
>
> > From: Spencer Baugh <sbaugh@catern.com>
> > Date: Fri, 10 Nov 2023 12:48:36 +0000 (UTC)
> > Cc: Spencer Baugh <sbaugh@janestreet.com>, dmitry@gutov.dev,
> >       66993@debbugs.gnu.org
> > 
> > > Thanks, that's what I thought: this loses information.  The "Cannot
> > > resolve lock conflict in batch mode" part is important, since it
> > > explains the "file-locked" part.  So please include the missing text
> > > in the list passed to 'signal' as its DATA argument, so as not to lose
> > > this explanation.
> > 
> > OK, how about this?  Which makes Emacs print:
> > 
> > Error: file-locked ("/home/sbaugh/file" "sbaugh@earth (pid 1852838)" "Cannot 
> > resolve lock conflict in batch mode")
> >   mapbacktrace(#f(compiled-function (evald func args flags) #<bytecode 
> > -0x1f22147a251783b>))
> >   debug-early-backtrace()
> >   debug-early(error (file-locked "/home/sbaugh/file" "sbaugh@earth (pid 
> > 1852838)" "Cannot resolve lock conflict in batch mode"))
> >   signal(file-locked ("/home/sbaugh/file" "sbaugh@earth (pid 1852838)" 
> > "Cannot resolve lock conflict in batch mode"))
> >   ask-user-about-lock("/home/sbaugh/file" "sbaugh@earth (pid 1852838)")
> >   write-region("foo" nil "~/file")
> >   eval((write-region "foo" nil "~/file") t)
> >   command-line-1(("--eval" "(write-region \"foo\" nil \"~/file\")"))
> >   command-line()
> >   normal-top-level()
> > /home/sbaugh/file: sbaugh@earth (pid 1852838), Cannot resolve lock conflict 
> > in batch mode
>
> Thanks, installed on master, and closing the bug.
>
>
> --- End Message ---