unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Nicolas Richard <theonewiththeevillook-Qt13gs6zZMY@public.gmane.org>
Cc: public-16879-ubl+/3LiMTaZdePnXv/OxA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
Subject: bug#16879: 24.3.50; Error running timer `font-latex-jit-lock-force-redisplay'
Date: Tue, 25 Feb 2014 15:18:11 +0100	[thread overview]
Message-ID: <86fvn7xom4.fsf@somewhere.org> (raw)
In-Reply-To: <87ppmbcn19.fsf-Qt13gs6zZMY@public.gmane.org> (Nicolas Richard's message of "Tue, 25 Feb 2014 14:57:54 +0100")



Hello Nicolas,

Nicolas Richard wrote:
> Sebastien Vauban writes:
>>   ╭────
>>   │ Error running timer `font-latex-jit-lock-force-redisplay':
>>   │ (wrong-number-of-arguments (2 . 2) 3) [2 times]
>>   ╰────
>
> The function `font-latex-jit-lock-force-redisplay' is provided by
> auctex. This bug was (temporarily) fixed in the auctex repository in
> commit 5b5ef6ee.
>
> Here's the commit msg:
>     * font-latex.el (font-latex-jit-lock-force-redisplay): Don't rely
>     on existing `jit-lock-force-redisplay' because recent bzr Emacs
>     broke compatibility changing the number of arguments.  Reported by
>     Robert Goldman.
>
> See also bug #14394
>
> The fix was temporary.
>
> Here's the more recent definition of
> font-latex-jit-lock-force-redisplay:
> (defun font-latex-jit-lock-force-redisplay (buf start end)
>   "Compatibility for Emacsen not offering `jit-lock-force-redisplay'."
>     ;; The following block is an expansion of `jit-lock-force-redisplay'
>     ;; and involved macros taken from CVS Emacs on 2007-04-28.
>     (with-current-buffer buf
>       (let ((modified (buffer-modified-p)))
> 	(unwind-protect
> 	    (let ((buffer-undo-list t)
> 		  (inhibit-read-only t)
> 		  (inhibit-point-motion-hooks t)
> 		  (inhibit-modification-hooks t)
> 		  deactivate-mark
> 		  buffer-file-name
> 		  buffer-file-truename)
> 	      (put-text-property start end 'fontified t))
> 	  (unless modified
> 	    (restore-buffer-modified-p nil))))))
>
> I suggest you update auctex -- but perhaps using the above definition
> will be sufficient.

AFAICT, I am up-to-date... with the `latex' ELPA package. Why isn't that
package redone, so that such fixes are distributed?

Anyway, I'm not really bothered by this problem. My goal was just
reporting it, so that it gets eventually fixed.

Thanks for your helpful answer.

Best regards,
  Seb

-- 
Sebastien Vauban






      parent reply	other threads:[~2014-02-25 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 13:34 bug#16879: 24.3.50; Error running timer `font-latex-jit-lock-force-redisplay' Sebastien Vauban
2014-02-25 13:57 ` Nicolas Richard
     [not found]   ` <87ppmbcn19.fsf-Qt13gs6zZMY@public.gmane.org>
2014-02-25 14:18     ` Sebastien Vauban [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86fvn7xom4.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=public-16879-ubl+/3LiMTaZdePnXv/OxA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
    --cc=theonewiththeevillook-Qt13gs6zZMY@public.gmane.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).