From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 14443@debbugs.gnu.org
Subject: bug#14443: 24.3.50; log-view-diff and log-view-diff-changeset broken in vc-bzr-change-log-mode and vc-annotate-mode (on w32)
Date: Thu, 23 May 2013 23:17:27 +0300 [thread overview]
Message-ID: <83ehcxsb6w.fsf@gnu.org> (raw)
In-Reply-To: <519E73D0.2090602@yandex.ru>
> Date: Thu, 23 May 2013 23:53:52 +0400
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: rgm@gnu.org, 14443@debbugs.gnu.org
>
> On 23.05.2013 20:52, Eli Zaretskii wrote:
> >> Date: Thu, 23 May 2013 20:46:07 +0400
> >> From: Dmitry Gutov <dgutov@yandex.ru>
> >> CC: 14443@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> >>
> >> I'm not sure how to find out.
> >
> > You could put a breakpoint on call-process and examine its arguments,
> > for example.
>
> I've rummaged around the manual a bit, and still don't understand what
> the recommended workflow is.
>
> Should I normally do `edebug-defun' before adding a breakpoint?
Actually, I meant GDB on the C level, but since you asked...
Yes, at least that's what I do.
> How do I display the value of a local variable?
C-x C-e with point after it, I guess. I'm quite sure it worked for me
when I used that last.
> How do I un-instrument a function? AFAICS, there are no commands like
> `edebug-cancel-', `-reset-' or `-remove-'.
Reload the .el file.
> Using diff.exe from the GnuWin32 collection is recommended, right?
That's what I use, yes.
next prev parent reply other threads:[~2013-05-23 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 22:22 bug#14443: 24.3.50; log-view-diff and log-view-diff-changeset broken in vc-bzr-change-log-mode and vc-annotate-mode (on w32) Dmitry Gutov
2013-05-23 7:25 ` Glenn Morris
2013-05-23 12:09 ` Dmitry Gutov
2013-05-23 16:09 ` Glenn Morris
2013-05-23 16:46 ` Dmitry Gutov
2013-05-23 16:52 ` Eli Zaretskii
2013-05-23 19:53 ` Dmitry Gutov
2013-05-23 20:17 ` Eli Zaretskii [this message]
2013-05-23 20:25 ` Dmitry Gutov
2013-05-23 16:59 ` Glenn Morris
2013-05-23 16:23 ` Eli Zaretskii
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=83ehcxsb6w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14443@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).