From: Karl Kleinpaste <Karl_Kleinpaste@APHRODITE.NECTAR.CS.CMU.EDU>
Subject: xemacs user sees trouble with gnus-vis
Date: Wed, 29 Nov 95 11:04:40 EST [thread overview]
Message-ID: <199511291605.RAA28158@ifi.uio.no> (raw)
Is anyone else out there familiar with the following failure mode
under xemacs?
The error raised is: wrong type argument, bufferp, ">>"
map-extents(#<byte-code (extent ignored) "@ \nC\fE\"FD\x0e\a$\a" [remove-text-properties start end extent-property extent text-prop nil buffer] 6> ">>" 0 2 nil nil text-prop)
set-text-properties(0 2 nil ">>")
gnus-cite-parse()
gnus-cite-parse-maybe()
gnus-article-add-buttons()
gnus-article-highlight-some()...
This person (not on the list, as you might guess) has gnus-visual set
to t, of course. He's running xemacs 19.13. He says he isn't using
anything like hilit19 or hl319. The error is apparently consistent in
articles containing citations.
Any clues welcome. I'd help him more if I could, but I'm an FSF GNU
Emacs user, not xemacs, and I know that text properties and
highlighting internals are supposed to be quite different between the
two.
--karl
next reply other threads:[~1995-11-29 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-29 16:04 Karl Kleinpaste [this message]
1995-11-29 21:03 ` Christopher Davis
1995-11-30 10:29 ` Peter Arius
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=199511291605.RAA28158@ifi.uio.no \
--to=karl_kleinpaste@aphrodite.nectar.cs.cmu.edu \
/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).