GNU bug report logs - #70526
29.2; package-vc-upgrade failed with error message "File is not under version control"

Previous Next

Full log

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

From: "Yi Yue" <include_yy <at> qq.com>
To: "Philip Kaludercic" <philipk <at> posteo.net>
Cc: 70526 <70526 <at> debbugs.gnu.org>
Subject: Re: bug#70526: 29.2;
 package-vc-upgrade failed with error message "File is not under
 version control"
Date: Wed, 24 Apr 2024 06:07:47 +0900

[Message part 1 (text/plain, inline)]

> (unrelated, but why do your messages include HTML entities?) (Sorry, I forgot to forbid the default formatter of my email client.) > My main fear is that this might have some unintended consequences. Of course. > I wouldn't want to rely on my understanding of vc either.  While it > would be easy to add a dynamic variable to indicate this behaviour, I am > careful not to overburden the abstractions that VC provides. Understand. I read the docstring of `vc-pull', which is used by `package-vc-upgrade'. It says: --------------------------------------------------------------------------   "Update the current fileset or branch. You must be visiting a version controlled file, or in a `vc-dir' buffer. ..." -------------------------------------------------------------------------- But `vc-dir' is a user command other than a function, it will open a  new buffer and return nil. In consideration of the fact that `vc-pull'  is an async function, it is not easy for us to kill the `vc-diff' buffer  right after the pull operation. As you suggested earlier, maybe we need to modify vc.el, making the restriction looser?  Also, I noticed that the maintainer bind `default-directory' in this commit: https://github.com/emacs-mirror/emacs/commit/7ab556b57631cb28db86b89ba296bc0599d9a399 Improve robustness of 'package-vc-update' Regards

[Message part 2 (text/html, inline)]

Previous Next

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