From: Ralf Angeli <angeli@caeruleus.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-auctex@gnu.org, 14394@debbugs.gnu.org,
Antoine Levitt <antoine.levitt@gmail.com>
Subject: bug#14394: [Bug-AUCTeX] bug#14394: jit-lock-force-redisplay redefinition breaks jit fontification in auctex
Date: Mon, 13 May 2013 18:57:51 +0200 [thread overview]
Message-ID: <87hai624xc.fsf__9735.26917300678$1368464329$gmane$org@caeruleus.net> (raw)
In-Reply-To: <83zjvy97w4.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 13 May 2013 19:11:55 +0300")
* Eli Zaretskii (2013-05-13) writes:
>> Second, this breaks function font-latex-jit-lock-force-redisplay in
>> auctex, which uses the old prototype. This is present in emacs and
>> auctex from trunk.
>
> The doc string fix issue aside, is there any reason why AUCTeX should
> call jit-lock-force-redisplay, instead of always using its expanded
> code, like it does for versions of Emacs that don't have that
> function?
I guess the idea was that calling the function might be more
forward-compatible than using the expanded code because this decouples
the code from future changes in the underlying machinery. In this
particular case this didn't work so well, but things can break with
either approach.
Mosè already changed the code in AUCTeX's repository to use the expanded
code only, so we might stick with this for the time being and see what
happens.
--
Ralf
next prev parent reply other threads:[~2013-05-13 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 9:23 bug#14394: jit-lock-force-redisplay redefinition breaks jit fontification in auctex Antoine Levitt
2013-05-13 16:11 ` Eli Zaretskii
2013-05-13 16:57 ` Ralf Angeli [this message]
2013-05-14 15:52 ` Stefan Monnier
2014-02-10 21:44 ` bug#14394: " Glenn Morris
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='87hai624xc.fsf__9735.26917300678$1368464329$gmane$org@caeruleus.net' \
--to=angeli@caeruleus.net \
--cc=14394@debbugs.gnu.org \
--cc=antoine.levitt@gmail.com \
--cc=bug-auctex@gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.