unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Aaron S. Hawley" <Aaron.Hawley@uvm.edu>
Subject: Re: log-view documentation
Date: Fri, 25 Nov 2005 19:41:42 -0500 (EST)	[thread overview]
Message-ID: <Pine.A41.4.58.0511251926260.65284@gnu.uvm.edu> (raw)
In-Reply-To: <E1Eemy4-0008WK-Lj@fencepost.gnu.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1751 bytes --]

On Wed, 23 Nov 2005, Richard M. Stallman wrote:

> Our style is to use @table @kbd for this.
> Please look at other such lists in the manual
> to see the proper style, especially for index entries
> and for giving the names of the commands.

That makes sense.  I was confused by the commands marked up as a list in
the "Old Versions" node -- no longer!

I've modified the patch to use the Texinfo table style.  I adopted (read:
copied)  and incorporated respectively the wording changes you've proposed
for documenting `vc-annotate'.  I also added some more cross references.
The patch is attached, but here's the table.

 @table @kbd

 @item p
 Move to the previous revision of the file.  A numeric prefix argument
 is a repeat count, so @kbd{C-u 10 p} would move backward 10 revisions.

 @item n
 Move to the next revision of the file.  A numeric prefix argument
 is a repeat count.

 @item f
 Visit the revision indicated at the current line, like typing @kbd{C-x
 v ~} and specifying the revision (@pxref{Old Versions}).

 @item d
 Display the diff (@pxref{Comparing Files}) between the revision
 indicated at the current line and the revision before it.  This is
 useful to see what actually changed when the revision indicated on the
 current line was committed.

 @item P
 Move 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 as a
 repeat count, so @kbd{C-u 10 P} would move backward 10 files.

 @item N
 Move to the log of the next file when there are logs for multiple
 files in the log buffer (@pxref{VC Dired Mode}).  It also takes a
 numeric prefix argument as a repeat count.

 @end table

[-- Attachment #2: log-view patch --]
[-- Type: TEXT/PLAIN, Size: 1894 bytes --]

--- files.texi	18 Nov 2005 13:54:05 -0500	1.122
+++ files.texi	25 Nov 2005 19:22:12 -0500	
@@ -1791,7 +1791,45 @@
   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.
+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:
+
+@table @kbd
+
+@item p
+Move to the previous revision of the file.  A numeric prefix argument
+is a repeat count, so @kbd{C-u 10 p} would move backward 10 revisions.
+
+@item n
+Move to the next revision of the file.  A numeric prefix argument
+is a repeat count.
+
+@item f
+Visit the revision indicated at the current line, like typing @kbd{C-x
+v ~} and specifying the revision (@pxref{Old Versions}).
+
+@item d
+Display the diff (@pxref{Comparing Files}) between the revision
+indicated at the current line and the revision before it.  This is
+useful to see what actually changed when the revision indicated on the
+current line was committed.
+
+@item P
+Move 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 as a
+repeat count, so @kbd{C-u 10 P} would move backward 10 files.
+
+@item N
+Move to the log of the next file when there are logs for multiple
+files in the log buffer (@pxref{VC Dired Mode}).  It also takes a
+numeric prefix argument as a repeat count.
+
+@end table
 
 @node VC Undo
 @subsubsection Undoing Version Control Actions

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  parent reply	other threads:[~2005-11-26  0:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 17:45 log-view documentation Aaron S. Hawley
2005-11-23  5:14 ` 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 [this message]
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.0511251926260.65284@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).