From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Loss of Fontification partway through file
Date: Thu, 19 Jun 2014 12:39:04 +0200 [thread overview]
Message-ID: <87tx7hp4jb.fsf@gmail.com> (raw)
In-Reply-To: CAA6UvuGy=qaOvCz9uc+2vMzPnFWJjKwfwX8TLauZYDSOXCdPSA@mail.gmail.com
Jacob Gerlach <jacobgerlach@gmail.com> writes:
> 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.
I did this too (save and kill the buffer and then find the file again),
again no issues, and even the issue described below disappeared ;)
What you describe reminds me a bit of fontification issues with
outshine.el, only that its just the opposite. When I find a file with
e.g .el extension (having stored `outline-minor-mode' in the major-mode
hook, and `outshine-hook-function' in the outline-minor-mode hook), the
buffer is fontified correctly right away.
But when I write some (outshine-style structured) content in a temp
buffer in e.g. fundamental-mode, and then call `emacs-lisp-mode' on that
buffer, the org-mode like headline-fontification is not there
immediately, I first have to do something (visibility cycling, add a
char or so...), then the 1st level headers turn blue ...
> 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"?
no idea, but this 'unfontification' of headline with '(...)' in them
happens quite frequently for me.
--
cheers,
Thorsten
prev parent reply other threads:[~2014-06-19 10:39 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
2014-06-19 10:39 ` Thorsten Jolitz [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tx7hp4jb.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@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/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).