unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "finalpatch" <fengli@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: pcvs log view not functional
Date: Sat, 26 Jul 2008 11:52:46 +1000	[thread overview]
Message-ID: <g6e01h$g5l$1@ger.gmane.org> (raw)
In-Reply-To: jwv63qtbwx3.fsf-monnier+emacs@gnu.org

If these commands do not work, i think they probably should be removed from 
the menu bar and C-x h m, because these are the most obvious places to find 
out what the user can do with a buffer.  I would really like to see these 
features working in a pcvs logview though. the ability to select a range in 
the log and diff it is so sweet.


"Stefan Monnier" <monnier@iro.umontreal.ca> wrote in message 
news:jwv63qtbwx3.fsf-monnier+emacs@gnu.org...
>> i just found that the logview window created from pressing "l" in a pcvs
>> buffer is a bit different from the logview window you get from "C-x v l" 
>> in
>> a source file buffer. all the functions (such as diff, annotate, find
>> version) in the logview menu doesnt work in the pcvs logview.  it's as if 
>> the
>> logview is not linked to the file and logview-mode cannot do anything 
>> with
>> it.
>
> I guess you tried to use the VC commands in the log view, and indeed
> they do not work.  You need to use the PCL-CVS commands instead if the
> log view comes from PCL-CVS.  The relevant prefix is C-x c, so C-x c =
> will do a diff (IIRC there's a = shortcut for it).  Sadly, PCL-CVS does
> not offer annotate, so that won't help you if you want to annotate
> the revision (tho you can do C-x c o to open the revision and then C-x
> v g to annotate it).
>
>
>        Stefan
>
>
>
> 






      parent reply	other threads:[~2008-07-26  1:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 14:06 pcvs log view not functional finalpatch
2008-07-25 19:14 ` Stefan Monnier
2008-07-26  1:07   ` Miles Bader
2008-07-26  3:36     ` Dan Nicolaescu
2008-07-26  5:10       ` Miles Bader
2008-07-26  1:52   ` finalpatch [this message]

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='g6e01h$g5l$1@ger.gmane.org' \
    --to=fengli@gmail.com \
    --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).