[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AUCTeX-devel] Fwd: Bug in font-latex.el

From: Robert Goldman
Subject: [AUCTeX-devel] Fwd: Bug in font-latex.el
Date: Fri, 10 May 2013 13:02:12 -0500
User-agent: Postbox 3.0.8 (Macintosh/20130427)

I submitted this bug to Aquamacs, because I encountered it there.  David
Reitter, the Aquamacs maintainer said I should pass it on to you.

I'm not sure that just dropping the BUF argument is enough, because I'm
not sure if START and END are buffer positions are markers.
JIT-LOCK-FORCE-REDISPLAY may need the latter.


-------- Original Message --------
Subject: Bug in font-latex.el
Date: Fri, 10 May 2013 12:34:04 -0500
From: Robert Goldman <address@hidden>
Reply-To: address@hidden
To: Development of Aquamacs Emacs <address@hidden>

font-latex.el has font-latex-jit-lock-force-redisplay whose docstring says:

"Compatibility for Emacsen not offering `jit-lock-force-redisplay'."

The first sexpression is as follows:

(defun font-latex-jit-lock-force-redisplay (buf start end)
  "Compatibility for Emacsen not offering `jit-lock-force-redisplay'."
  (if (fboundp 'jit-lock-force-redisplay)
      (jit-lock-force-redisplay buf start end)

but when I look at the source for jit-lock-force-redisplay (in
jit-lock.el.gz), I see that it takes only two arguments (start and end),
not BUF.  Interestingly, its docstring mentions a BUF argument, which
suggests it was recently updated without the docstring getting updated.

I think we need simply drop that BUF argument.  jit-lock-force-redisplay
extracts the right buffer from the start and end markers.

GNU Emacs (x86_64-apple-darwin10.8.0, NS apple-appkit-1038.36)
 of 2013-05-07 on asura.local - Aquamacs Distribution 3.xdev

Hope that helps,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]