GNU bug report logs - #66993
[PATCH] project.el: avoid asking user about project-list-file lock

Previous Next

Full log

Message #65 received at 66993 <at> debbugs.gnu.org (full text, mbox):

From: Spencer Baugh <sbaugh <at> janestreet.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: dmitry <at> gutov.dev, 66993 <at> debbugs.gnu.org
Subject: Re: bug#66993: [PATCH] project.el: avoid asking user about
 project-list-file lock
Date: Wed, 08 Nov 2023 12:05:38 -0500

Eli Zaretskii <eliz <at> gnu.org> writes:
>> From: Spencer Baugh <sbaugh <at> janestreet.com>
>> Cc: Dmitry Gutov <dmitry <at> gutov.dev>,  66993 <at> debbugs.gnu.org
>> Date: Wed, 08 Nov 2023 10:41:15 -0500
>> 
>> > If that's the case, just catch the error and retry, several times,
>> > perhaps with variable delays.
>> 
>> Perhaps, but it would be nice to do that by catching specifically
>> file-locked rather than catching all errors.
>
> Not sure I follow: userlock.el signals a very specific error, doesn't
> it?  Or what am I missing?

By that you mean file-locked?  It only signals file-locked if it first
prompts the user, which is what we want to avoid.  If noninteractive=t,
then it just signals error:

(if noninteractive (error "Cannot resolve lock conflict in batch mode"))

Possibly we should just change that to signal file-locked too.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.