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: Dmitry Gutov <dmitry <at> gutov.dev>
Cc: sbaugh <at> janestreet.com, 66993 <at> debbugs.gnu.org
Subject: bug#66993: [PATCH] project.el: avoid asking user about project-list-file lock
Date: Wed, 08 Nov 2023 15:50:34 +0200

> Date: Wed, 8 Nov 2023 15:26:11 +0200
> Cc: 66993 <at> debbugs.gnu.org
> From: Dmitry Gutov <dmitry <at> gutov.dev>
> 
> On 08/11/2023 14:22, Eli Zaretskii wrote:
> >> From: Spencer Baugh<sbaugh <at> janestreet.com>
> >> Date: Tue, 07 Nov 2023 16:28:04 -0500
> >>
> >> There are several features which will cause Emacs to frequently call
> >> project-current, and therefore call project-remember-project, and
> >> therefore sometimes call project--write-project-list whenever a new
> >> project is seen.
> > Why does project-current immediately writes the list to the file?  Why
> > cannot it keep the information in memory and write it only when the
> > session ends, or at some random rare opportunity?
> 
> It could indeed be written from kill-emacs-hook, or just the next time 
> an opportunity presents.
> 
> With the latter approach, though, it would be handier if the 
> lock-prompter signaled a specific error we could catch to reschedule saving.

Why do you need an error when you can use file-locked-p to check up
front that the file is locked?

Previous Next

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