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

Previous Next

Full log

View this message in rfc822 format

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

> From: Spencer Baugh <sbaugh <at> janestreet.com>
> Cc: dmitry <at> gutov.dev,  66993 <at> debbugs.gnu.org
> Date: Wed, 08 Nov 2023 12:05:38 -0500
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> >
> > 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"))

And that is not specific enough?

And why the noninteractive=t case is relevant here, btw?

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

Or something else.  If needed.

In any case, these are minor details, the main point is that this
error can be caught.

Previous Next

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