all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Kyle Meyer <kyle@kyleam.com>
Cc: 22399@debbugs.gnu.org, Rasmus <rasmus@gmx.us>,
	Phillip Lord <phillip.lord@russet.org.uk>
Subject: bug#22399: org-mode fontification
Date: Tue, 26 Jan 2016 08:06:29 -0500	[thread overview]
Message-ID: <jwvmvrsv6ci.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87lh7cu8r0.fsf@kyleam.com> (Kyle Meyer's message of "Tue, 26 Jan 2016 01:58:59 -0500")

>> I see the problem.  org-src-font-lock-fontify-block is using buffers
>> named " org-src-fontification:<major-mode>" in an unusual way:
>> they're updated via normal buffer modifications, but they're not put in
>> font-lock-mode, so all the font-lock machinery which tries to keep the
>> fontification up-to-date is short-circuited, so it triggers a bug in
>> font-lock-ensure where we made incorrect assumptions.
>> I installed the patch below into emacs-25, which should fix this
>> problem,
> Thank you.  That seems to work nicely.
> Is there anything else I need to do for the first patch?

No, it's good to go.  If you don't have commit rights, I can install it
for you into emacs-25, unless the Org guys prefer to do it via the
Org tree.


        Stefan





  parent reply	other threads:[~2016-01-26 13:06 UTC|newest]

Thread overview: 48+ 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
2016-01-18 18:05   ` Phillip Lord
2016-01-18 18:05   ` Phillip Lord
2016-01-18 18:48     ` Rasmus
2016-01-18 18:48     ` Rasmus
2016-01-18 19:27       ` Kyle Meyer
2016-01-19  6:32         ` Kyle Meyer
2016-01-19  8:51           ` Rasmus
2016-01-19 15:33             ` Kyle Meyer
2016-01-19 18:04               ` Kyle Meyer
2016-01-19 18:04               ` Kyle Meyer
2016-01-19 19:05               ` Rasmus
2016-01-20 11:39                 ` Phillip Lord
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-20 22:02                     ` Stefan Monnier
2016-01-21  0:44                       ` Kyle Meyer
2016-01-21  0:44                       ` Kyle Meyer
2016-01-25 14:30                         ` Stefan Monnier
2016-01-26  6:58                           ` Kyle Meyer
2016-01-26  6:58                           ` Kyle Meyer
2016-01-26 13:06                             ` Stefan Monnier
2016-01-26 13:06                             ` Stefan Monnier [this message]
2016-01-26 15:27                               ` Kyle Meyer
2016-01-26 15:27                               ` Kyle Meyer
2016-02-01 13:50                                 ` Stefan Monnier
2016-02-01 13:50                                 ` Stefan Monnier
2016-02-03  6:38                                   ` Bastien Guerry
2016-02-03  6:38                                   ` Bastien Guerry
2016-02-03  6:51                                     ` Kyle Meyer
2016-02-03  6:51                                     ` Kyle Meyer
2016-02-03  6:55                                       ` Bastien Guerry
2016-02-03  6:55                                       ` Bastien Guerry
2016-02-11 18:18                                         ` Phillip Lord
2016-02-11 18:18                                         ` Phillip Lord
2016-01-25 14:30                         ` Stefan Monnier
2016-01-20 17:18                   ` Kyle Meyer
2016-01-19 19:05               ` Rasmus
2016-01-19 15:33             ` Kyle Meyer
2016-01-19  8:51           ` Rasmus
2016-01-19  6:32         ` Kyle Meyer
2016-01-19  6:32           ` Kyle Meyer
2016-01-19 11:25           ` Phillip Lord
2016-01-19 11:25           ` Phillip Lord
2016-01-19  6:32         ` Kyle Meyer
2016-01-18 19:27       ` Kyle Meyer

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=jwvmvrsv6ci.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=22399@debbugs.gnu.org \
    --cc=kyle@kyleam.com \
    --cc=phillip.lord@russet.org.uk \
    --cc=rasmus@gmx.us \
    /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.