xemacs user sees trouble with gnus-vis

xemacs user sees trouble with gnus-vis

[Karl Kleinpaste]

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

Re: xemacs user sees trouble with gnus-vis

[Christopher Davis]

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.

Re: xemacs user sees trouble with gnus-vis

[Peter Arius]

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