From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: C-x v g going further back in time? Date: Mon, 26 Jan 2004 16:44:54 GMT Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1075135905 2972 80.91.224.253 (26 Jan 2004 16:51:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 26 Jan 2004 16:51:45 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jan 26 17:51:41 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Al9xc-0008Vo-00 for ; Mon, 26 Jan 2004 17:51:41 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1Al9vw-0002Yu-4X for geh-help-gnu-emacs@m.gmane.org; Mon, 26 Jan 2004 11:49:56 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!cyclone.bc.net!snoopy.risq.qc.ca!charlie.risq.qc.ca!53ab2750!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 14 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Original-NNTP-Posting-Host: 132.204.24.84 Original-X-Complaints-To: abuse@umontreal.ca Original-X-Trace: charlie.risq.qc.ca 1075135494 132.204.24.84 (Mon, 26 Jan 2004 11:44:54 EST) Original-NNTP-Posting-Date: Mon, 26 Jan 2004 11:44:54 EST Original-Xref: shelby.stanford.edu gnu.emacs.help:120428 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:16374 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:16374 > I was actually thinking of putting the cache logic into > `vc-print-log', which can be invoked independently of the 'C-x v g', > 'C-x o', 'L' path. But I think if they invoke 'C-x v l' directly, How 'bout splitting "the cache logic" into "setting up the cache info" (done in vc-print-log) and checking the cache (done in `L' only if you don't want it to happen in `C-x v g') ? The caching should not depend on the buffer's name. Making it possible to display logs in a different buffer would probably be good, but it should be a completely independent decision. Stefan