Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: Re: issues with read-only summary buffers
Date: Tue, 08 Feb 2011 11:42:09 -0800	[thread overview]
Message-ID: <sd7hdauxda.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <87bp2m2wp2.fsf@keller.adm.naquadah.org> (Julien Danjou's message of "Tue, 08 Feb 2011 11:03:59 +0100")

>>>>> On Tue, 08 Feb 2011 11:03:59 +0100, Julien Danjou <julien@danjou.info> said:

>> 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?

JD> Remove read-only from `debug-ignored-errors'.

Ah ha!  Thanks!
-- 
Wes Hardaker                                     
My Pictures:  http://capturedonearth.com/
My Thoughts:  http://pontifications.hardakers.net/



  reply	other threads:[~2011-02-08 19:42 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
2011-02-08 19:42   ` Wes Hardaker [this message]
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=sd7hdauxda.fsf@wjh.hardakers.net \
    --to=wes@hardakers.net \
    --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).