emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: emacs-orgmode@gnu.org, e.fraga@ucl.ac.uk
Cc: Bastien <bzg@gnu.org>
Subject: Re: Bug: org-block face isn't applied to special blocks
Date: Mon, 14 Sep 2020 17:17:19 +0200	[thread overview]
Message-ID: <f3d44297-276f-f1a1-8249-ef585fa02c99@posteo.eu> (raw)
In-Reply-To: <87pn6s7did.fsf@ucl.ac.uk>

As far as src blocks being treated differently, there's already the 
~org-src-block-faces~ variable.

How about the following :

  + Make the ~org-block~ face apply to every block
  + either
    - add an ~org-src-block~ face
    - modify ~org-src-block-faces~ to allow a catch-all case
    It'd be nice for those to apply to unrecognized languages
  + keep ~org-fontify-quote-and-verse-blocks~

I think the only users that would notice the difference are the few (?) 
who use special blocks and expect them not to be fontified.
All they'd have to do to restore the previous behavior is set the 
~org-src-block~ and unset the ~org-block~ faces.

>> It isn't applied
>>   - to src blocks, when the language isn't recognized
>>   - to special blocks (that is, blocks with arbitrary names)
>> I make heavy use of special blocks and I'd like this face to apply to them.
> I also make heavy use of special blocks but, for me, these are often
> more like verse or quote blocks (i.e. the contents of the block are
> prose) than src blocks so I would not want them to be treated as src
> blocks are.  I think we'll need to have (yet) another option to control
> this?

  reply	other threads:[~2020-09-14 17:01 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 [this message]
2020-09-13 20:23         ` Bastien

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:

  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=f3d44297-276f-f1a1-8249-ef585fa02c99@posteo.eu \
    --to=sebastien.miquel@posteo.eu \
    --cc=bzg@gnu.org \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \


* 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


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).