unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: log-view documentation
Date: Thu, 24 Nov 2005 19:06:48 +1300	[thread overview]
Message-ID: <17285.22648.602817.559583@kahikatea.snap.net.nz> (raw)
In-Reply-To: <E1Ef8El-0007Tw-2n@fencepost.gnu.org>

 > Here I have put that table into our usual format.
 > I have also tried clearing up certain descriptions
 > whose meaning I was not certain of.  I am partly guessing
 > (since I don't use this feature), so if any of this is wrong,
 > could someone tell me?

I've not used it much, but it seems OK to me.

 ...
 > @item J
 > Annotate the revision indicated by the current line.
 > 
 > @item A
 > Annotate the revision before the one indicated by the current line.
 > This is useful to see the state the file was in before the change on
 > the current line was made.

I think you might look at the revision indicated by the current line before
the previous one (which can currently be done with `J' then `P'.

How about using A for annotating the revision indicated by the current line
(its more mnemonic) and C-u A for the revision before the one indicated by the
current line?  Tthis feature is not in Emacs 21, so now would be a good time to
change it.

Nick

  reply	other threads:[~2005-11-24  6:06 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 [this message]
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=17285.22648.602817.559583@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=emacs-devel@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).