From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: vc-find-revision-no-save? Date: Mon, 24 Oct 2022 17:10:49 -0400 Message-ID: References: <878rl543co.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29656"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Dmitry Gutov , John Yates , Emacs developers To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 24 23:32:06 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1on53G-0007Uf-9j for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Oct 2022 23:32:06 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1on4iv-0005T0-Nx; Mon, 24 Oct 2022 17:11:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1on4io-0005QV-7C for emacs-devel@gnu.org; Mon, 24 Oct 2022 17:10:58 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1on4ik-0004BH-FW for emacs-devel@gnu.org; Mon, 24 Oct 2022 17:10:56 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 12294441F80; Mon, 24 Oct 2022 17:10:53 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 89DDF441BF8; Mon, 24 Oct 2022 17:10:51 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1666645851; bh=uwufkQK80XNbPMAolAV09qEJTZD9h9SAyaqCslAOlVM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=STgc2oUtOYV5+pg3o3gfZ4O8EG0foEBLgY34EL/EBpndS/38ftdeuz6R3PdY3ELlX TLWI2PMV10OmXbTiV0S5YzuVpvefU0b6apMHgk5f7XZ5d1mN+WRZmrIKWocDFL7625 /UxehqYTIcdQeSRin2+gRt9fkFvvi8nLYUzKkXGK0pCj6ztleMMbYIXb0BK2qnjUYz h9EN2iZKLuz741wVNB4zOmnUuES4Si0uMKR+Gn3yj0/Q6bqUg77OeGDzQB2E9xbrMq pyi/A7gjg8kTrIN6ZFw6HmHkfVbEakOnuaZ/1zOhZgA6dYx4AFvHAcmg4rszaTdk2z tef1cDLuO6nBQ== Original-Received: from alfajor (modemcable219.124-130-66.mc.videotron.ca [66.130.124.219]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id CFAFC120FA2; Mon, 24 Oct 2022 17:10:50 -0400 (EDT) In-Reply-To: <878rl543co.fsf@posteo.net> (Philip Kaludercic's message of "Mon, 24 Oct 2022 16:02:15 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:298427 Archived-At: Philip Kaludercic [2022-10-24 16:02:15] wrote: > Dmitry Gutov 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. Stefan