From: Rasmus <rasmus@gmx.us>
To: 22399@debbugs.gnu.org
Subject: bug#22399: org-mode fontification
Date: Mon, 18 Jan 2016 15:16:48 +0100 [thread overview]
Message-ID: <87ziw36khb.fsf@gmx.us> (raw)
In-Reply-To: <87oacjng36.fsf@russet.org.uk>
Hi Phillip,
Thanks for your report.
phillip.lord@russet.org.uk (Phillip Lord) writes:
> On emacs-25 ox-html, line 1847, org-html-fontify-code does this...
>
> (setq code (with-temp-buffer
> ;; Switch to language-specific mode.
> (funcall lang-mode)
> (insert code)
> ;; Fontify buffer.
> (org-font-lock-ensure)
>
>
> But `org-font-lock-ensure' is defined like so....
>
> (defalias 'org-font-lock-ensure
> (if (fboundp 'org-font-lock-ensure)
> #'font-lock-ensure
> (lambda (_beg _end) (font-lock-fontify-buffer))))
>
>
> which takes two args, causing crashes when exporting to code to HTML.
This is fixed in the most recent stable version of Org, i.e. 8.3.3¹ ,
which, I guess, will be part of if Emacs 25.2 or 26.1 (whichever comes
first and allow new features). It’s also fixed in 8.2.10². I guess
Emacs-25 should switch v8.2.10. [Honestly, when v8.3 couldn’t be merged I
did not cross my mind to upgrade to v8.2.10]. In case v8.2.10 it too
radical, a "local fix" must be applied to the version of Org in emacs.git.
Thanks,
Rasmus
Footnotes:
¹ http://orgmode.org/cgit.cgi/org-mode.git/tree/lisp/ox-html.el?h=maint#n2086
² http://orgmode.org/cgit.cgi/org-mode.git/tree/lisp/ox-html.el?id=fdd9b18598239dd0e8b18383ac930110d51ed22e#n1893
--
Warning: Everything saved will be lost
next prev parent reply other threads:[~2016-01-18 14:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 13:59 bug#22399: org-mode fontification Phillip Lord
2016-01-18 14:16 ` Rasmus [this message]
2016-01-18 18:05 ` Phillip Lord
2016-01-18 18:48 ` Rasmus
[not found] ` <87bn8i7mha.fsf@gmx.us>
2016-01-18 19:27 ` Kyle Meyer
[not found] ` <87d1syvgc7.fsf@kyleam.com>
2016-01-19 6:32 ` Kyle Meyer
2016-01-19 11:25 ` Phillip Lord
[not found] ` <8737tu13la.fsf__5430.1016768024$1453185240$gmane$org@kyleam.com>
2016-01-19 8:51 ` Rasmus
[not found] ` <87d1sy54vt.fsf@gmx.us>
2016-01-19 15:33 ` Kyle Meyer
[not found] ` <87wpr5zirr.fsf@kyleam.com>
2016-01-19 18:04 ` Kyle Meyer
2016-01-19 19:05 ` Rasmus
[not found] ` <871t9d4cg3.fsf@gmx.us>
2016-01-20 11:39 ` bug#22399: [O] " Phillip Lord
2016-01-20 17:18 ` Kyle Meyer
2016-01-20 22:02 ` Stefan Monnier
2016-01-21 0:44 ` Kyle Meyer
[not found] ` <87oacf92wl.fsf@kyleam.com>
2016-01-25 14:30 ` Stefan Monnier
2016-01-26 6:58 ` Kyle Meyer
2016-01-26 13:06 ` Stefan Monnier
2016-01-26 15:27 ` Kyle Meyer
2016-02-01 13:50 ` Stefan Monnier
2016-02-03 6:38 ` Bastien Guerry
2016-02-03 6:51 ` Kyle Meyer
2016-02-03 6:55 ` Bastien Guerry
2016-02-11 18:18 ` Phillip Lord
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=87ziw36khb.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=22399@debbugs.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 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).