emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Jacob Gerlach <jacobgerlach@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Loss of Fontification partway through file
Date: Thu, 19 Jun 2014 05:47:54 -0400	[thread overview]
Message-ID: <CAA6UvuGy=qaOvCz9uc+2vMzPnFWJjKwfwX8TLauZYDSOXCdPSA@mail.gmail.com> (raw)
In-Reply-To: <87y4wtcpz9.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

>
> The MWE (with native fontification -> t) looks ok for me,

Thanks for taking time to check this. I should note that if I find a new
file (test.org) and yank the MWE, it is fontified correctly, but if I save
and kill the buffer and then find the file again, that is when the problem
occurs. In general, if I make a change that brings back the fontification,
it doesn't disappear again until freshly finding the file.


> the only
> fontification issue I see (and not only in your MWE) is that headline
>
> ,----
> | * Heading with some add-to-list's (some commented)
> `----
>
> looses its font due to the "list" in it -> '(some commented)'.
> I see that often in my Org files - as soon as I type parens in a
> headline it turn white.
>
> I do not observe the same. Since it is outside of an emacs-lisp source
block, why would it be interpreted as a "list"?

>

>
> ,----
> | Org-mode version 8.2.7 (release_8.2.7-1096-g23496c @
> | /usr/share/emacs/24.3/lisp/org/lisp/)
> `----
>
> --
> cheers,
> Thorsten
>
> Thanks,
Jake

[-- Attachment #2: Type: text/html, Size: 2281 bytes --]

next prev parent reply	other threads:[~2014-06-19  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  0:41 Loss of Fontification partway through file Jacob Gerlach
2014-06-19  7:34 ` Thorsten Jolitz
2014-06-19  9:47   ` Jacob Gerlach [this message]
2014-06-19 10:39     ` Thorsten Jolitz

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.orgmode.org/

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

  git send-email \
    --in-reply-to='CAA6UvuGy=qaOvCz9uc+2vMzPnFWJjKwfwX8TLauZYDSOXCdPSA@mail.gmail.com' \
    --to=jacobgerlach@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tjolitz@gmail.com \
    /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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).