unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: VC top of the tree diff and log
Date: Wed, 8 Jul 2009 23:48:53 -0700 (PDT)	[thread overview]
Message-ID: <200907090648.n696mrou001146@godzilla.ics.uci.edu> (raw)
In-Reply-To: <buo8wiytv2e.fsf@dhlpc061.dev.necel.com> (Miles Bader's message of "Thu, 09 Jul 2009 12:05:29 +0900")

Miles Bader <miles@gnu.org> writes:

  > Dan Nicolaescu <dann@ics.uci.edu> writes:
  > >   > Would be useful, though I dunno what you'd bind it too... at some point
  > >   > having too many bindings for essentially-similar-commands becomes kind
  > >   > of annoying/confusing.
  > >
  > > I am thinking that we could have 2 modes for the log: 
  > > - a short one that would be used by default for directory logs
  > > - the current long one that would be used for file logs
  > > (I haven't completely thought this through)...
  > 
  > I normally am interested in exactly the same thing from either file or
  > project logs:  detailed info about the last few changesets.  I use short
  > logs too (when I'm trying to discover longer-term trends instead of
  > detailed info), but there seems no connection with whether I restrict
  > the scope to a file or not.
  > 
  > What sounds nice to me would be a quick "toggle log mode" binding in the
  > log display buffer (with caching so it's fast, and smart preservation of
  > point position in the log, etc), or maybe even better, a "toggle
  > detailed info for this entry" binding, but maybe those aren't so easy to
  > implement in emacs...  [Hmm... "*" comes to mind for some reason, though
  > I have no idea why...]

Toggling between long and short logs for the whole log is not hard.
I can implement this, the we can decide on the UI 

I am not convinced that "toggle detailed info for this entry" is very
useful.  If the detailed info is displayed in a different window, it
should not be too hard either (if the underlying VCS has some easy way to
retrieve such info).


  > As far as global vs. file logs, I think maybe I'd prefer to _always_ get
  > global logs in git/svn/... but with some slight hint about the file when
  > invoked from a file buffer -- e.g., maybe display entries not related to
  > the file in a "dim" face, and initially position the cursor on the first
  > modification to the file, etc.  My reasoning is that I don't think I
  > really mean "show me the history of this file", when I use "C-x v l",
  > but rather "show me recent history of the project, given that I happen
  > to be in a file in that project".  [Real file logs would be nice too,
  > when there's too much chaff, but they seem secondary, rather than
  > primary.]

I don't want to see global history when looking at a file , the VCS does
not matter.
After working with source trees that are > 1GB and tens of thousands of
files...




  parent reply	other threads:[~2009-07-09  6:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 18:45 VC top of the tree diff and log Dan Nicolaescu
2009-07-08  2:50 ` Miles Bader
2009-07-08 21:10   ` Dan Nicolaescu
2009-07-08 23:01     ` Miles Bader
2009-07-09  0:29       ` Dan Nicolaescu
2009-07-09  3:05         ` Miles Bader
2009-07-09  3:58           ` C-x v l in a dired buffer [was: Re: VC top of the tree diff and log] Dan Nicolaescu
2009-07-09  6:48           ` Dan Nicolaescu [this message]
2009-07-16 21:38       ` VC top of the tree diff and log Dan Nicolaescu
2009-07-18 21:45         ` Juri Linkov
2009-07-11 19:51 ` Stefan Monnier
2009-07-23  5:43   ` Dan Nicolaescu
2009-07-30  7:18     ` Dan Nicolaescu
2009-08-29 19:13       ` Dan Nicolaescu
2009-08-29 21:25         ` Stefan Monnier
2009-08-29 22:47           ` Juri Linkov
2009-08-29 23:10             ` Miles Bader
2009-09-01 21:36               ` Juri Linkov
2009-09-01 22:27                 ` Juri Linkov
2009-09-04  0:04                   ` Juri Linkov
2009-09-04  2:12                   ` Stefan Monnier
2009-08-30  6:16           ` Dan Nicolaescu
2009-09-01 21:35             ` Juri Linkov
2009-09-01 22:07               ` Dan Nicolaescu
2009-09-02  4:13                 ` Miles Bader
2009-09-02  4:34                   ` Dan Nicolaescu
2009-09-04  0:05                     ` Juri Linkov
2009-09-04  0:33                       ` Miles Bader
2009-09-01 21:41         ` Juri Linkov
2009-09-01 22:46           ` Dan Nicolaescu
2009-09-04  0:06             ` Juri Linkov
2009-12-06 22:37           ` Dan Nicolaescu
2009-09-04  0:36         ` Juri Linkov
2009-09-04  3:42           ` Miles Bader

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=200907090648.n696mrou001146@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).