From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: git-blame.el won't run
Date: Wed, 21 Feb 2007 14:55:31 +0100 [thread overview]
Message-ID: <87vehvsjho.fsf@morpheus.local> (raw)
In-Reply-To: 13478.1172059706@localhost
Xavier Maillard <zedek@gnu.org> writes:
> Hi,
>
> This is the backtrace after C-g (after a few minutes):
>
>
> Debugger entered--Lisp error: (quit)
> process-send-region(#<process git-blame> 1 28910)
> (let ((display-buf ...) (blame-buf ...) (args ...)) (if startline (setq args ...)) (setq args (append args ...)) (setq git-blame-proc (apply ... "git-blame" blame-buf "git" "blame" args)) (with-current-buffer blame-buf (erase-buffer) (make-local-variable ...) (make-local-variable ...) (setq git-blame-file display-buf) (setq git-blame-current nil)) (set-process-filter git-blame-proc (quote git-blame-filter)) (set-process-sentinel git-blame-proc (quote git-blame-sentinel)) (process-send-region git-blame-proc (point-min) (point-max)) (process-send-eof git-blame-proc))
> (if git-blame-proc (message "Already running git blame") (let (... ... ...) (if startline ...) (setq args ...) (setq git-blame-proc ...) (with-current-buffer blame-buf ... ... ... ... ...) (set-process-filter git-blame-proc ...) (set-process-sentinel git-blame-proc ...) (process-send-region git-blame-proc ... ...) (process-send-eof git-blame-proc)))
> git-blame-run()
> (progn (let (...) (if ... ... ...)) (setq git-blame-cache (make-hash-table :test ...)) (git-blame-run))
> (if git-blame-mode (progn (let ... ...) (setq git-blame-cache ...) (git-blame-run)) (cancel-timer git-blame-idle-timer))
> git-blame-mode(nil)
> call-interactively(git-blame-mode)
> execute-extended-command(nil)
> call-interactively(execute-extended-command)
If you switch to the buffer called " git blame for <filename>" (notice
the leading space, you will probably see a usage/error message from
git.
Maybe your git blame doesn't like the --incremental flag or the
--contents flag. But the problem is that I'm not sure how to make
emacs not hang.
process-send-region blocks when sending the file contents, since git
isn't reading it. But git finishes, so emacs should be able to detect
that there is no process that can read anything anymore.
--
David Kågedal
next prev parent reply other threads:[~2007-02-21 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 22:35 git-blame.el won't run Xavier Maillard
2007-02-16 18:14 ` Xavier Maillard
2007-02-19 20:42 ` David Kågedal
2007-02-19 21:32 ` Xavier Maillard
2007-02-20 1:59 ` Jakub Narebski
2007-02-20 7:50 ` David Kågedal
2007-02-20 17:28 ` Xavier Maillard
2007-02-20 17:34 ` David Kågedal
2007-02-21 12:08 ` Xavier Maillard
2007-02-21 13:55 ` David Kågedal [this message]
2007-02-21 17:21 ` Xavier Maillard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vehvsjho.fsf@morpheus.local \
--to=davidk@lysator.liu.se \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).