From: Julien Danjou <julien@danjou.info>
To: Wes Hardaker <wes@hardakers.net>
Cc: ding@gnus.org
Subject: Re: issues with read-only summary buffers
Date: Tue, 08 Feb 2011 11:03:59 +0100 [thread overview]
Message-ID: <87bp2m2wp2.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <sd4o8f8rx4.fsf@wjh.hardakers.net>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Mon, Feb 07 2011, Wes Hardaker wrote:
> I'd try and find out where the errors are getting generated from, but
> (setq debug-on-error t) doesn't seem to consider read-only violations as
> errors, so I can't get a stack trace. Anyone know how to accomplish
> getting a stack trace for read-only errors?
Remove read-only from `debug-ignored-errors'.
--
Julien Danjou
❱ http://julien.danjou.info
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-02-08 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 21:18 Wes Hardaker
2011-02-07 21:22 ` Wes Hardaker
2011-02-08 10:03 ` Julien Danjou [this message]
2011-02-08 19:42 ` Wes Hardaker
2011-02-08 23:37 ` Wes Hardaker
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=87bp2m2wp2.fsf@keller.adm.naquadah.org \
--to=julien@danjou.info \
--cc=ding@gnus.org \
--cc=wes@hardakers.net \
/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).