From: arius@immd2.informatik.uni-erlangen.de (Peter Arius)
Subject: Re: xemacs user sees trouble with gnus-vis
Date: 30 Nov 1995 11:29:09 +0100 [thread overview]
Message-ID: <s44rayqgzuy.fsf@faui21i.informatik.uni-erlangen.de> (raw)
In-Reply-To: Christopher Davis's message of Wed, 29 Nov 1995 16:03:23 -0500 (EST)
>>>>> In article <199511292103.QAA03852@loiosh.kei.com>,
>>>>> "Christopher" == Christopher Davis <ckd@loiosh.kei.com> writes:
KK> == Karl Kleinpaste <Karl_Kleinpaste@APHRODITE.NECTAR.CS.CMU.EDU> Is
KK> anyone else out there familiar with the following failure mode under
KK> xemacs?
KK> The error raised is: wrong type argument, bufferp, ">>"
KK> set-text-properties(0 2 nil ">>")
Christopher> Known bug in the text-properties compatibility stuff shipped
Christopher> in 19.13.
Christopher> Change lisp/utils/text-props.el and re-byte-compile.
Christopher> [patch deleted]
Sorry Christopher, but that version is broken, too (as I have already
reported to the XEmacs newsgroup). Please use
(defun set-text-properties (start end props &optional buffer)
"You should NEVER use this function. It is ideologically blasphemous.
It is provided only to ease porting of broken FSF Emacs programs."
(if (stringp buffer)
nil
(map-extents #'(lambda (extent ignored)
(remove-text-properties start end
(list (extent-property extent
'text-prop)
nil)
buffer))
buffer start end nil nil 'text-prop)
(add-text-properties start end props buffer)))
which will probably go into XEmacs 19.14, according to a note from Ben Wing.
Cheers,
Peter
--
This one's tricky. You have to use imaginary numbers, like eleventeen...
-Calvin
prev parent reply other threads:[~1995-11-30 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-29 16:04 Karl Kleinpaste
1995-11-29 21:03 ` Christopher Davis
1995-11-30 10:29 ` Peter Arius [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=s44rayqgzuy.fsf@faui21i.informatik.uni-erlangen.de \
--to=arius@immd2.informatik.uni-erlangen.de \
/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).