unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Benjamin Rutt <brutt+news@bloomington.in.us>
Subject: Re: C-x v g going further back in time?
Date: Sun, 25 Jan 2004 19:38:35 -0500	[thread overview]
Message-ID: <wc3brorczn8.fsf@mu.cis.ohio-state.edu> (raw)
In-Reply-To: jwvu12q6lhl.fsf-monnier+gnu.emacs.help@asado.iro.umontreal.ca

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> In case you didn't notice it on the emacs-devel mailing list,
>> something similar to the first of your two wishes has now been
>> implemented in CVS emacs, using the 'L' and 'D' keys for log and diff,
>> respectively.
>
> Yes, this is becoming really neat.  And since this is like a magic lantern,
> I'll just make another wish: that the new `L' key only calls `cvs log' if
> the *vc* buffer doesn't already contain the proper log info: this way you
> can repeatedly do `L' without each time having to wait the minute-or-so it
> takes to get the complete log info.

My first cut at your feature request didn't go so well; it's tough for
two reasons:

1) the *vc* buffer is used both for 'C-x v l' and also when you do
   'C-x v v' to commit a file, so it might contain either info that
   your commit was successful, or the actual log info...would it be OK
   to change 'C-x v l' to write to something other than the *vc*
   buffer, say the *vc-commit-history* buffer?

2) cache coherency problem.  What if the log info is updated b/c of
   new commits?  Do you always want the outdated log info?

Any comments on these issues?  Thanks,
-- 
Benjamin

  reply	other threads:[~2004-01-26  0:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 21:45 C-x v g going further back in time? Benjamin Rutt
2004-01-08 22:14 ` Andrew Taylor
2004-01-08 22:16 ` Benjamin Rutt
2004-01-08 22:47   ` Stefan Monnier
2004-01-21  1:02     ` Benjamin Rutt
2004-01-21  3:18       ` Stefan Monnier
2004-01-26  0:38         ` Benjamin Rutt [this message]
2004-01-26 14:28           ` Stefan Monnier
2004-01-26 15:03             ` Benjamin Rutt
2004-01-26 16:44               ` Stefan Monnier
2004-01-26 18:33               ` Stefan Monnier
2004-01-12  2:55   ` Benjamin Rutt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wc3brorczn8.fsf@mu.cis.ohio-state.edu \
    --to=brutt+news@bloomington.in.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).