From: Christopher Davis <ckd@loiosh.kei.com>
Cc: ding@ifi.uio.no
Subject: Re: xemacs user sees trouble with gnus-vis
Date: Wed, 29 Nov 1995 16:03:23 -0500 (EST) [thread overview]
Message-ID: <199511292103.QAA03852@loiosh.kei.com> (raw)
In-Reply-To: <199511291605.RAA28158@ifi.uio.no>
KK> == Karl Kleinpaste <Karl_Kleinpaste@APHRODITE.NECTAR.CS.CMU.EDU>
KK> Is anyone else out there familiar with the following failure mode
KK> under xemacs?
KK> The error raised is: wrong type argument, bufferp, ">>"
KK> set-text-properties(0 2 nil ">>")
Known bug in the text-properties compatibility stuff shipped in 19.13.
Change lisp/utils/text-props.el and re-byte-compile.
--- text-props.el~ Wed Aug 30 19:36:48 1995
+++ text-props.el Wed Sep 6 22:42:51 1995
@@ -303,14 +303,16 @@
(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."
- (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))
+ (if (and (stringp buffer) (not (setq buffer (get-buffer 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)))
\f
;;; The following functions can probably stay in lisp, since they're so simple.
next prev parent reply other threads:[~1995-11-29 21:03 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 [this message]
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=199511292103.QAA03852@loiosh.kei.com \
--to=ckd@loiosh.kei.com \
--cc=ding@ifi.uio.no \
/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).