Re: vc-find-revision-no-save?

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Dmitry Gutov <dgutov@yandex.ru>,  John Yates <john@yates-sheets.org>,
>  Emacs developers <emacs-devel@gnu.org>
> Date: Mon, 24 Oct 2022 17:10:49 -0400
> 
> Philip Kaludercic [2022-10-24 16:02:15] wrote:
> > Dmitry Gutov <dgutov@yandex.ru> writes:
> >> On 24.10.2022 03:27, John Yates wrote:
> >>> Notice that the default is nil.  What is the logic in allowing an
> >>> historic revision to be associated with a file?  Why is it not merely
> >>> a readonly buffer with no backing file?
> 
> I can answer this one: because back when we wrote this code, the "Git"
> of the day was called "CVS" and getting a historic revision required
> fetching it from the centralized server, so you were usually quite happy
> to keep a local copy, even if you had to erase them manually every once
> in a while.
> 
> > If that is the motivation, is there a reason the files are stored on the
> > current working directory, instead of using /tmp or ~/.cache?  I have
> > set that option to t which is a great improvement IMO, as I don't want
> > to fill up my working directory with temporary files.
> 
> I suspect the default should be changed, indeed.

Could the default be backend-dependent?  Then people who use the VCSes
where you are "quite happy to keep a local copy" will still have their
cake.  That'd include CVS and SVN, I think.