From: "Tanis, Craig" <Craig-Tanis@utc.edu>
To: Kyle Meyer <kyle@kyleam.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: src block face [8.3.1 (8.3.1-56-g17a225-elpaplus @ /Users/ctanis/.emacs.d/elpa/org-plus-contrib-20150817/)]
Date: Tue, 18 Aug 2015 14:55:53 +0000 [thread overview]
Message-ID: <AC673793-1A41-4660-84D4-70A4FEC7B82D@utc.edu> (raw)
In-Reply-To: <87a8to1x5v.fsf@kyleam.com>
Aha! In my configuration, I was fontifying org-block to use a different background color and font family. I don't suppose there's some way to get the best of both worlds: visibly distinct org-blocks with mode-specific keyword fontification?
Thanks,
Craig
> On Aug 18, 2015, at 10:36 AM, Kyle Meyer <kyle@kyleam.com> wrote:
>
> "Tanis, Craig" <Craig-Tanis@utc.edu> writes:
>
>> SRC blocks don't show correct face when a language is specified.
>>
>> #+begin_src
>> correctly shows in 'org-block face
>> #+end_src
>>
>> #+begin_src language
>> incorrectly shows in 'default face
>> #+end_src
>
> I suspect that in your second block you're using text the would have the
> default face in a buffer for that language.
>
> Depending on the value of org-src-fontify-natively, Org will try to
> highlight the block according to the language.
>
> So
>
> #+begin_src
> (message "yes")
> #+end_src
>
> will use the org-block face, but
>
> #+begin_src elisp
> (message "yes")
> #+end_src
>
> will highlight according to emacs-lisp-mode.
>
> If org-src-fontify-natively is nil, the org-block face will be used for
> the second block as well.
>
> --
> Kyle
----
Craig Tanis, Ph.D.
UTC Computer Science
craig-tanis@utc.edu
next prev parent reply other threads:[~2015-08-18 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 23:24 Bug: src block face [8.3.1 (8.3.1-56-g17a225-elpaplus @ /Users/ctanis/.emacs.d/elpa/org-plus-contrib-20150817/)] Tanis, Craig
2015-08-18 14:36 ` Kyle Meyer
2015-08-18 14:55 ` Tanis, Craig [this message]
2015-08-18 15:23 ` 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
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=AC673793-1A41-4660-84D4-70A4FEC7B82D@utc.edu \
--to=craig-tanis@utc.edu \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.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
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).