From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: vc-annotate error
Date: Fri, 07 Apr 2006 18:40:35 -0600 [thread overview]
Message-ID: <e170ri$vrb$1@sea.gmane.org> (raw)
In-Reply-To: <pan.2006.04.07.23.28.15.308299@as.arizona.edu>
JD Smith wrote:
> vc-annotate is giving me a similar error as was reported earlier for
> vc.el revision 1.408:
>
> (file-error "Cannot open load file" "vc-nil")
>
> This occurs because I have specified a default annotate mode of
> 'fullscale, and the `vc-annotate-display-autoscale' function still
> relies on the variable `vc-annotate-backend' to call the appropriate
> backend time functions I wrote years ago. This was formerly a global
> variable, but Stefan's changes to `vc-annotate' circa 1.408 made it buffer
> local:
>
> (with-current-buffer temp-buffer-name
> (set (make-local-variable 'vc-annotate-backend) (vc-backend file))
> (set (make-local-variable 'vc-annotate-parent-file) file)
> (set (make-local-variable 'vc-annotate-parent-rev) rev)
> (set (make-local-variable 'vc-annotate-parent-display-mode)
> display-mode))
That snippet immediately follows this:
(with-output-to-temp-buffer temp-buffer-name
(vc-call annotate-command file (get-buffer temp-buffer-name) rev))
So could the problem be that those variables are set _after_ the
annotate buffer contents have been inserted and displayed (via
temp-buffer-show-function -> vc-annotate-display-select)? Shouldn't
they be set before?
> For whatever reason, these are not currently being set in the annotate
> output buffer, which breaks the auto-scaling annotation display, since
> it doesn't know the backend to use. I haven't figured out how the
> buffer-local variables are being lost. Other annotate display modes
> don't have backend-specific functions, so they continue to work.
Are you sure they're not being set at all, vs. being set too late?
--
Kevin Rodgers
next prev parent reply other threads:[~2006-04-08 0:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 23:28 vc-annotate error JD Smith
2006-04-08 0:40 ` Kevin Rodgers [this message]
2006-04-08 1:36 ` JD Smith
2006-04-10 22:00 ` vc-annotate error, PATCH JD Smith
2006-04-10 22:27 ` Stefan Monnier
2006-04-10 22:59 ` JD Smith
2006-04-11 16:57 ` Richard Stallman
2006-04-11 18:02 ` JD Smith
2006-04-11 18:34 ` Dan Nicolaescu
2006-04-11 19:02 ` JD Smith
2006-04-11 19:19 ` Dan Nicolaescu
2006-04-12 17:09 ` Richard Stallman
2006-04-12 19:17 ` JD Smith
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='e170ri$vrb$1@sea.gmane.org' \
--to=ihs_4664@yahoo.com \
/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).