From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gemini Lasswell <gazally@runbox.com>
Cc: 31051@debbugs.gnu.org
Subject: bug#31051: 26.0.91; Error in Edebug when debugging inline-letevals
Date: Sun, 21 Jul 2019 15:41:02 +0200 [thread overview]
Message-ID: <878ssr7bf5.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87v9vw8k8j.fsf@runbox.com> (Gemini Lasswell's message of "Sat, 20 Jul 2019 14:33:00 -0700")
Gemini Lasswell <gazally@runbox.com> writes:
> Here's a revised patch, which for me fixes both the short example and
> instrumenting lisp/net/shr.el:
Thanks; applied.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-07-21 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 18:47 bug#31051: 26.0.91; Error in Edebug when debugging inline-letevals Gemini Lasswell
2019-07-13 16:08 ` Lars Ingebrigtsen
2019-07-20 21:33 ` Gemini Lasswell
2019-07-21 13:41 ` Lars Ingebrigtsen [this message]
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=878ssr7bf5.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=31051@debbugs.gnu.org \
--cc=gazally@runbox.com \
/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).