From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: stack overflow in regexp matcher.
Date: Mon, 20 Dec 2010 20:07:59 +0100 [thread overview]
Message-ID: <m3wrn48dps.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <loom.20101220T191956-662@post.gmane.org>
Mac Wooster <bgmrao@gmail.com> writes:
> Lars:
> A large buffer, I have pasted the a snippet. But, essentially, I don't see any "errors".
>
> Thanks for the help
>
>
> * 5702 FETCH (UID 21068 RFC822.SIZE 58997 BODYSTRUCTURE
> (("TEXT" "PLAIN" ("CHARSET" "UTF-8")
I think something has folded something.
Could you just attach the buffer as an, er, attachment and mail it to
me?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-20 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 17:57 bgmrao
2010-12-20 18:00 ` Lars Magne Ingebrigtsen
2010-12-20 18:24 ` Mac Wooster
2010-12-20 19:07 ` Lars Magne Ingebrigtsen [this message]
2010-12-21 2:59 ` bgmrao
2010-12-21 3:00 ` Mac Wooster
-- strict thread matches above, loose matches on Subject: below --
2010-12-07 20:03 John Sullivan
2010-12-07 20:26 ` Lars Magne Ingebrigtsen
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=m3wrn48dps.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).