From: Lars Ingebrigtsen <larsi@gnus.org>
To: lee <lee@yun.yagibdah.de>
Cc: 18572@debbugs.gnu.org
Subject: bug#18572: unbalanced parentheses
Date: Wed, 25 Jan 2017 21:22:09 +0100 [thread overview]
Message-ID: <87sho6j3f2.fsf@gnus.org> (raw)
In-Reply-To: <87wq8ps3e3.fsf@yun.yagibdah.de> (lee's message of "Sat, 27 Sep 2014 13:34:44 +0200")
Sorry for the late response; the bug report has been sitting in a part
of the bug tracker that nobody has looked at due to a misunderstanding.
lee <lee@yun.yagibdah.de> writes:
> I was writing a follow-up to [1] and got the following in the debugger
> (null-characters replaced with '.'):
>
> Debugger entered--Lisp error: (scan-error "Unbalanced parentheses" 204 275)
> signal(scan-error ("Unbalanced parentheses" 204 275))
> byte-code("\b\204\b. \203..\304\n@\nA\"\210\202..\305\306\307\v\310\311#\"\210\304\207" [debug-on-quit debug-on-error err orig-text signal error "Invalid data for rfc2047 encoding: %s" mm-replace-in-string "[ \n]+" " "] 6)
> rfc2047-encode-region(176 275)
> mail-encode-encoded-word-buffer()
> message-send-mail(nil)
> message-send-via-mail(nil)
> message-send(nil)
> message-send-and-exit(nil)
> funcall-interactively(message-send-and-exit nil)
> call-interactively(message-send-and-exit nil nil)
> command-execute(message-send-and-exit)
>
> This seems to be caused by a header inserted by gnus:
>
> In-Reply-To: <5425FA38.8070801@gcal.net> ("Philippe "Clérié\"'s" message of "Fri,
> 26 Sep 2014 19:43:52 -0400")
I've now fixed this on the Emacs trunk.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next parent reply other threads:[~2017-01-25 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wq8ps3e3.fsf@yun.yagibdah.de>
2017-01-25 20:22 ` Lars Ingebrigtsen [this message]
2017-01-26 16:11 ` bug#18572: unbalanced parentheses Richard Stallman
2017-01-26 16:14 ` Lars 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
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=87sho6j3f2.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=18572@debbugs.gnu.org \
--cc=lee@yun.yagibdah.de \
/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).