From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: Re: issues with read-only summary buffers
Date: Tue, 08 Feb 2011 15:37:22 -0800 [thread overview]
Message-ID: <sdei7irtcd.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <sd7hdauxda.fsf@wjh.hardakers.net> (Wes Hardaker's message of "Tue, 08 Feb 2011 11:42:09 -0800")
>>>>> On Tue, 08 Feb 2011 11:42:09 -0800, Wes Hardaker <wes@hardakers.net> said:
>>>>> 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'.
WH> Ah ha! Thanks!
Drat. It is my code (my gnus-highlight code that was never integrated
into the main release but I live by it).
The question is, why is placing a text-property on existing text
triggering a read-only error. Grumble.
Debugger entered--Lisp error: (buffer-read-only #<buffer *Summary nnimap+hardakers:ucd-snmp.mail*>)
gnus-put-text-property(56 60 face gnus-highlight-autoface-bg-\#c0c0ff)
gnus-put-text-property-excluding-characters-with-faces(56 60 face gnus-highlight-autoface-bg-\#c0c0ff)
#[(def) "\b?\205^\306 @!\205^ A;\203\0\307 ABC\202\0 A\310\n\236A\206%\311\224\206+\312 \310\n\236A\2064\311\225\206:\313 \314\n\236\211\203K\315A!\210\202T\316\v\f\317\320\n!$\210\300\n\236\205]\321\211+\207" [stop def facedata start end result looking-at bg match 1 point-at-bol point-at-eol sub gnus-highlight-line-by-expression gnus-put-text-property-excluding-characters-with-faces face gnus-highlight-get-face t] 6]((".*\\(snmp\\)" . "#c0c0ff"))
mapcar(#[(def) "\b?\205^\306 @!\205^ A;\203\0\307 ABC\202\0 A\310\n\236A\206%\311\224\206+\312 \310\n\236A\2064\311\225\206:\313 \314\n\236\211\203K\315A!\210\202T\316\v\f\317\320\n!$\210\300\n\236\205]\321\211+\207" [stop def facedata start end result looking-at bg match 1 point-at-bol point-at-eol sub gnus-highlight-line-by-expression gnus-put-text-property-excluding-characters-with-faces face gnus-highlight-get-face t] 6] ((".*\\(teststring\\)" (fg . "blue2") (bg . "green1")) ("^*" . "green") ("^=>" . "#ffdddd") ("^......[^EOR].^[^[]*\\[\\([^]]+\\)\\]" (bg . "yellow")) ("^......[^EOR]./[^[]*\\[\\([^]]+\\)\\]" (fg . "brown2")) ("^......[^EOR].\\+[^[]*\\[\\([^]]+\\)\\]" . "#b0e0ff") ("^\\(......\\).*no-99$" (bg . "yellow3")) ("^\\(......\\).*no$" (bg . "yellow")) ("^\\(......\\).*ham(-99|)$" (bg . "#90d0c0")) ("^\\(......\\).*spam(-99|)$" (bg . "orange")) (".*\\(\\[Closed\\]\\)" (bg . "orange")) (".*\\(snmp\\)" . "#c0c0ff")))
gnus-highlight-line-by-expression()
run-hooks(gnus-summary-update-hook)
apply(run-hooks gnus-summary-update-hook)
--
Wes Hardaker
My Pictures: http://capturedonearth.com/
My Thoughts: http://pontifications.hardakers.net/
prev parent reply other threads:[~2011-02-08 23:37 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
2011-02-08 23:37 ` Wes Hardaker [this message]
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=sdei7irtcd.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).