From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 13434@debbugs.gnu.org
Subject: bug#13434: 24.3.50; Replying to an HTML email yields "Text is read-only"
Date: Mon, 21 Jan 2013 17:17:52 +0100 [thread overview]
Message-ID: <877gn61pe7.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: <jwvk3r65ysr.fsf-monnier+emacs@gnu.org>
Hallöchen!
Stefan Monnier writes:
>> Sorry, setting debug-on-error doesn't change Emacs' behaviour. I
>> see no debugger and no backtrace. At least, there was no buffer
>> with such a name or something similar.
>
> It's probably caught by debug-ignored-errors.
> Try to additionally do M-: (setq debug-ignored-errors nil) RET before
> reproducing the bug.
Yes, this was it. Here is the result:
Debugger entered--Lisp error: (text-read-only)
erase-buffer()
gnus-copy-article-buffer()
gnus-post-news(nil "nnml:KFA" [14582 #("Einladung: Telekon Marl-Jülich (23 Jan 15:00 CET)" 0 49 (charset windows-1252)) "paul.woebkenberg@***" "Fri, 18 Jan 2013 10:43:04 +0100" "<5764054.113668.1358502196387.JavaMail.trustmail@seem-ap1>" "" 85896 1807 "wilson KFA:14582" ((To . "bronger@physik.rwth-aachen.de, r.carius@***, s.muthmann@***") (Cc . "odo.***@***"))] "*Article nnml:KFA*" (14582) nil nil)
gnus-summary-followup((14582) nil)
gnus-summary-followup-with-original(nil)
call-interactively(gnus-summary-followup-with-original nil nil)
I replaced some confidential data with "***".
Tschö,
Torsten.
--
Torsten Bronger Jabber ID: torsten.bronger@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
next prev parent reply other threads:[~2013-01-21 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 10:37 bug#13434: 24.3.50; Replying to an HTML email yields "Text is read-only" Torsten Bronger
2013-01-14 18:35 ` Lars Magne Ingebrigtsen
2013-01-21 10:47 ` Torsten Bronger
2013-01-21 15:42 ` Stefan Monnier
2013-01-21 16:17 ` Torsten Bronger [this message]
2013-07-06 17:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gn61pe7.fsf@physik.rwth-aachen.de \
--to=bronger@physik.rwth-aachen.de \
--cc=13434@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
/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.