From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, sds@gnu.org, emacs-devel@gnu.org
Subject: Re: more candidates for obsoletion
Date: Tue, 04 Sep 2012 15:29:56 -0400 [thread overview]
Message-ID: <jwvzk551td5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mx15oe0x.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 04 Sep 2012 20:10:06 +0200")
>> - You might prefer to use fast_string_match.
> Fixed and fixed. And then I don't have to save the match data either, I
> guess?
Indeed.
>> - Is the recursive debugging a problem you've found to show up
>> unavoidably all the time, or are you just being cautious?
> It is a real problem. My first test case used a string that the
> debugger used, too, so Emacs went into an infinite debugging loop...
>> - You could turn your `debugging' into a Lisp var (call it
>> "inhibit-debug-on-message"), or you could let-bind debug-on-message to
>> nil around the call to the debugger.
> Sounds good. I've had a peek around the sources, but I can't quite see
> how to let-bind something from C. What should I be looking for as an
> example?
IIRC debug-on-error and debug-on-quit are let-bound to nil in the Elisp
part of the code, so you should do that as well (see debug.el).
Otherwise, `specbind' is the magic function to use from C.
Stefan
next prev parent reply other threads:[~2012-09-04 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 6:43 more candidates for obsoletion Glenn Morris
2012-05-01 19:51 ` Sam Steingold
2012-05-01 22:06 ` Juanma Barranquero
2012-05-01 22:25 ` Lars Magne Ingebrigtsen
2012-05-01 22:28 ` Lars Magne Ingebrigtsen
2012-05-02 13:02 ` Stefan Monnier
2012-05-13 18:34 ` Lars Magne Ingebrigtsen
2012-05-14 2:20 ` Stefan Monnier
2012-09-04 18:10 ` Lars Ingebrigtsen
2012-09-04 19:29 ` Stefan Monnier [this message]
2012-09-04 21:24 ` Lars Ingebrigtsen
2012-05-02 5:03 ` Thierry Volpiatto
2012-05-02 9:25 ` Michael Albinus
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=jwvzk551td5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=lekktu@gmail.com \
--cc=sds@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 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.