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

> From: Spencer Baugh <sbaugh <at> catern.com>
> Date: Sat, 18 Nov 2023 23:10:43 +0000 (UTC)
> Cc: dmitry <at> gutov.dev, sbaugh <at> janestreet.com, 66993 <at> debbugs.gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> >> But actually, maybe it's time that we just enable savehist by default.
> >
> > Even if we decide to do that (and I'm not at all sure we should), how
> > would that solve the difficulty pointed out by Dmitry?  Even if
> > savehist is ON by default, the user could turn it OFF, right?
> 
> That's fine, we'd still be preserving backwards-compatibility:
> project--list would still be saved by default.  The user could turn it
> off, if they want, but that's not a problem - they can turn it off if
> they want.

IMNSHO, it is a very bad idea to have one feature turn on and off as a
side effect of another, unrelated feature.  We should not have such
inelegant dependencies.  savehist is a general-purpose feature which
saves the history of important user actions, whereas the history of
projects is a completely different feature from a much more narrow
area of user activities.  They should not depend on one another, not
directly anyway.

Previous Next

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