GNU bug report logs - #11528
24.0.97; [PATCH] enriched-next-annotation: wrong-type-argument number-or-marker-p nil

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Leo <sdl.web <at> gmail.com>
Subject: bug#11528: closed (Re: bug#11528: 24.0.97; [PATCH]
 enriched-next-annotation: wrong-type-argument number-or-marker-p nil)
Date: Sat, 23 Jun 2012 13:44:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#11528: 24.0.97; [PATCH] enriched-next-annotation: wrong-type-argument number-or-marker-p nil

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 11528 <at> debbugs.gnu.org.

-- 
11528: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11528
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Leo <sdl.web <at> gmail.com>
To: 11528-done <at> debbugs.gnu.org
Subject: Re: bug#11528: 24.0.97;
	[PATCH] enriched-next-annotation: wrong-type-argument
	number-or-marker-p nil
Date: Sat, 23 Jun 2012 21:39:27 +0800

Fixed in emacs-24.

[Message part 3 (message/rfc822, inline)]

From: Leo <sdl.web <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.0.97; [PATCH] enriched-next-annotation: wrong-type-argument
	number-or-marker-p nil
Date: Mon, 21 May 2012 11:10:50 +0800

[Message part 4 (text/plain, inline)]

Yidong, could this buglet be fixed in emacs-24? This could stop people
from opening malformed enriched text files.

  Emacs -q bug-enriched.txt

| Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
|   enriched-next-annotation()
|   ......

[bug-enriched.txt (text/enriched, inline)]

[Message part 6 (text/plain, inline)]

diff --git a/lisp/textmodes/enriched.el b/lisp/textmodes/enriched.el
index 68a99b0e..a28fcfc7 100644
--- a/lisp/textmodes/enriched.el
+++ b/lisp/textmodes/enriched.el
@@ -437,7 +437,7 @@ (defun enriched-next-annotation ()
 	      (progn (goto-char (match-beginning 0))
 		     (not (looking-at enriched-annotation-regexp))))
     (forward-char 1)
-    (if (= ?< (char-after (point)))
+    (if (eq ?< (char-after (point)))
 	(delete-char 1)
       ;; A single < that does not start an annotation is an error,
       ;; which we note and then ignore.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.