emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-block face isn't applied to special blocks
Date: Sun, 13 Sep 2020 22:23:20 +0200	[thread overview]
Message-ID: <87r1r5ifyf.fsf@gnu.org> (raw)
In-Reply-To: <b55ada30-634f-e3a9-9c2c-641779cb091d@posteo.eu> ("Sébastien Miquel"'s message of "Thu, 10 Sep 2020 20:17:59 +0200")

Hi Sébastien,

Sébastien Miquel <sebastien.miquel@posteo.eu> writes:

> As far as I can tell, with 8a083514a7 from master, the situation is
> now as follows.
>
> The org-block face is applied
>  - to src blocks, when the language is recognized
>  - to example, export blocks
>  - to verse and quote blocks, if ~org-fontify-quote-and-verse-blocks~
> is ~t~.
>
> It isn't applied
>  - to src blocks, when the language isn't recognized
>  - to special blocks (that is, blocks with arbitrary names)

Exact.

> I make heavy use of special blocks and I'd like this face to apply to them.
> I think it would make more sense than the current behavior, and is
> less surprising. (It is also more in line with the previous
> docstring).
>
> (I also think it should apply to unrecognized src blocks)

I agree there is room for improvement, but I'm not sure on what we
should be aiming for.

-- 
 Bastien


      parent reply	other threads:[~2020-09-13 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29 20:05 Bug: org-block face isn't applied to special blocks Sébastien Miquel
2020-09-04 16:14 ` Bastien
2020-09-04 17:47   ` Sébastien Miquel
2020-09-07  5:32     ` Bastien
2020-09-10 18:17       ` Sébastien Miquel
2020-09-11 11:34         ` Eric S Fraga
2020-09-14 15:17           ` Sébastien Miquel
2020-09-13 20:23         ` Bastien [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=87r1r5ifyf.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastien.miquel@posteo.eu \
    /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).