From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
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: Fri, 24 May 2013 00:25:39 +0400 [thread overview]
Message-ID: <519E7B43.5050301@yandex.ru> (raw)
In-Reply-To: <83ehcxsb6w.fsf@gnu.org>
On 24.05.2013 0:17, Eli Zaretskii wrote:
>>> 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...
Oh. Though I believe it's called something like `Fcall_process' there.
>> 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.
Then I guess you've used it in a buffer without lexical-binding.
>> How do I un-instrument a function? AFAICS, there are no commands like
>> `edebug-cancel-', `-reset-' or `-remove-'.
>
> Reload the .el file.
Thanks! It's kind of an obvious solution, but I could've spent quite a
while looking for a specialized command.
next prev parent reply other threads:[~2013-05-23 20:25 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
2013-05-23 20:25 ` Dmitry Gutov [this message]
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=519E7B43.5050301@yandex.ru \
--to=dgutov@yandex.ru \
--cc=14443@debbugs.gnu.org \
--cc=eliz@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).