From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: a.s@realize.ch, emacs-devel@gnu.org
Subject: Re: Revise etc/DEBUG documentation
Date: Sat, 03 Sep 2016 18:27:41 +0300 [thread overview]
Message-ID: <8337lhdmvm.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-9oKnMhr1hAsX_fFkQT2Ke3BVWX-ocFB7i7-OUBM7d2rA@mail.gmail.com> (message from Noam Postavsky on Sat, 3 Sep 2016 11:05:20 -0400)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Sat, 3 Sep 2016 11:05:20 -0400
> Cc: Alain Schneble <a.s@realize.ch>, Emacs developers <emacs-devel@gnu.org>
>
> > 'Fsignal' is a very useful place to put a breakpoint in. All Lisp
> > errors go through there. If you are only interested in errors that
> > would fire the debugger, breaking at 'maybe_call_debugger' is useful.
>
> I think it would be better to explicitly say "would fire the lisp
> debugger" here, as "the debugger" mostly refers to GDB in this file.
Good idea; done.
next prev parent reply other threads:[~2016-09-03 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 10:31 Revise etc/DEBUG documentation Alain Schneble
2016-09-03 11:31 ` Eli Zaretskii
2016-09-03 13:14 ` Alain Schneble
2016-09-03 13:45 ` Noam Postavsky
2016-09-03 14:35 ` Eli Zaretskii
2016-09-03 21:56 ` Alain Schneble
2016-09-03 14:34 ` Eli Zaretskii
2016-09-03 15:05 ` Noam Postavsky
2016-09-03 15:27 ` Eli Zaretskii [this message]
2016-09-03 21:51 ` Alain Schneble
2016-09-04 14:42 ` Eli Zaretskii
2016-09-04 16:24 ` Alain Schneble
2016-09-05 16:36 ` Eli Zaretskii
2016-09-05 17:00 ` Eli Zaretskii
2016-09-05 19:19 ` Alain Schneble
2016-09-05 19:35 ` Alain Schneble
2016-09-06 2:39 ` Eli Zaretskii
2016-09-06 10:06 ` Alain Schneble
2016-09-06 15:16 ` Eli Zaretskii
2016-09-06 16:14 ` Alain Schneble
2016-09-06 16:54 ` Alain Schneble
2016-09-06 21:52 ` Davis Herring
2016-09-07 17:39 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8337lhdmvm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=a.s@realize.ch \
--cc=emacs-devel@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.