From: "Aaron S. Hawley" <Aaron.Hawley@uvm.edu>
Subject: log-view documentation
Date: Tue, 22 Nov 2005 12:45:53 -0500 (EST) [thread overview]
Message-ID: <Pine.A41.4.58.0511221240120.111796@gnu.uvm.edu> (raw)
log-view is pretty cool. it should be documented.
A proposal is below. It is copied (via Kill and Yank) from the commands
documented for the "annotate buffer", found in the "Old Versions" section
of the manual.
--- files.texi 18 Nov 2005 13:54:05 -0500 1.122
+++ files.texi 22 Nov 2005 12:32:38 -0500
@@ -1790,8 +1790,50 @@
@findex vc-print-log
To view the detailed version control status and history of a file,
type @kbd{C-x v l} (@code{vc-print-log}). It displays the history of
-changes to the current file, including the text of the log entries. The
-output appears in a separate window.
+changes to the current file, including the text of the log entries. The
+output appears in a separate window. The point is centered at the
+revision of the file that was currently visited.
+
+From the change log buffer, the following keys can be used to move
+between the logs of files and revisions, to view past revisions, and
+to view diffs:
+
+@itemize @bullet
+
+@item
+Pressing @kbd{p} moves to the previous revision of the file. It also
+takes a numeric prefix argument, so for example @kbd{C-u 10 p} would
+take you back 10 revisions.
+
+@item
+Pressing @kbd{n} moves to the next revision of the file. It also
+takes a numeric prefix argument, so for example @kbd{C-u 10 n} would
+take you forward 10 revisions.
+
+@item
+Pressing @kbd{f} visits the revision at the current line, like typing
+@kbd{C-x v ~} and specifying the revision.
+
+@item
+Pressing @kbd{d} shows the diff of the revision at line with its
+previous revision. This is useful to see what actually changed when
+the revision denoted on the current line was committed.
+
+@item
+Pressing @kbd{P} moves to the log of the previous file. when there
+are multiple files in the log buffer (@pxref{VC Dired Mode}).
+Otherwise, it moves to the beginning of the log. It also takes a
+numeric prefix argument, so for example @kbd{C-u 10 P} would take you
+back 10 files.
+
+@item
+Pressing @kbd{N} moves to the log of the next file if there are logs
+for multiple files in the log buffer (@pxref{VC Dired Mode}).
+Otherwise, it moves to the end of the log. It also takes a numeric
+prefix argument, so for example @kbd{C-u 10 N} would take you forward
+10 files.
+
+@end itemize
@node VC Undo
@subsubsection Undoing Version Control Actions
next reply other threads:[~2005-11-22 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 17:45 Aaron S. Hawley [this message]
2005-11-23 5:14 ` log-view documentation Richard M. Stallman
2005-11-23 8:08 ` Nick Roberts
2005-11-24 3:57 ` Richard M. Stallman
2005-11-24 6:06 ` Nick Roberts
2005-11-25 15:49 ` Richard M. Stallman
2005-11-25 21:59 ` Nick Roberts
2005-11-26 0:45 ` Aaron S. Hawley
2005-11-26 0:41 ` Aaron S. Hawley
2005-11-26 16:21 ` Richard M. Stallman
[not found] <E1EmOvm-0006dY-1f@fencepost.gnu.org>
2005-12-14 6:09 ` Aaron S. Hawley
2005-12-14 10:08 ` Juri Linkov
2005-12-14 18:45 ` Aaron S. Hawley
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=Pine.A41.4.58.0511221240120.111796@gnu.uvm.edu \
--to=aaron.hawley@uvm.edu \
/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).