emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Takafumi Arakaki <aka.tkf@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Use font-lock-face property in org-src-font-lock-fontify-block?
Date: Fri, 28 Sep 2012 12:24:15 +0200	[thread overview]
Message-ID: <CAPM+gBSC8Cwy78aXXVkn20FhzSuAAPxSsoN3h2WpJ-Mcnn8qnQ@mail.gmail.com> (raw)
In-Reply-To: <87mx0aprjf.fsf@bzg.ath.cx>

Hi Bastien,

Thanks. I will bundle my version of the function in my module while
watching development of org-src.el.  I will report again if I find
something.

Takafumi


On Fri, Sep 28, 2012 at 8:53 AM, Bastien <bzg@altern.org> wrote:
> Hi Takafumi,
>
> Takafumi Arakaki <aka.tkf@gmail.com> writes:
>
>> I am thinking about including my version of
>> org-src-font-lock-fontify-block in EIN, but Dan Davison suggested to
>> ask in this ML because it could be a problem in org-mode too.
>
> I'm not sure I understand the problem you are trying to fix for your own
> code here but things work fine here in Org.
>
>> Does anyone know what is happening here?
>
> Not really.   Do you always need this or is it just for some modes?
> Maybe those modes use `font-lock-face' while other modes use `face'
> and highlighting in Src Blocks would need to add `font-lock-face' in
> the first case while just adding `face' in  the second one.
>
> Perhaps adding both is some extra security...  but I'd rather wait
> for a real bug in Org :)
>
> Thanks anyway for reporting this,
>
> --
>  Bastien

      reply	other threads:[~2012-09-28 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 10:55 [PATCH] Use font-lock-face property in org-src-font-lock-fontify-block? Takafumi Arakaki
2012-09-28  6:53 ` Bastien
2012-09-28 10:24   ` Takafumi Arakaki [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=CAPM+gBSC8Cwy78aXXVkn20FhzSuAAPxSsoN3h2WpJ-Mcnn8qnQ@mail.gmail.com \
    --to=aka.tkf@gmail.com \
    --cc=bzg@altern.org \
    --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).