From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: emacs-orgmode@gnu.org
Subject: Couple of issues with org block meta lines faces
Date: Fri, 10 Jul 2020 11:23:30 +0200 [thread overview]
Message-ID: <9fb38135-dc45-2d46-be0b-de9c297ac686@posteo.eu> (raw)
Hi,
If you start emacs as follows, making sure emacs picks up the latest org
from org-plus-contrib, and with file.org being the content of this mail,
#+BEGIN_SRC sh :async
emacs -q \
--eval "(defface org-block-begin-line '((t (:background \"blue\"
:height 0.8))) \"\")" \
--eval "(setq org-fontify-whole-block-delimiter-line t)" \
file.org
#+END_SRC
You may observe the following issues:
1) begin-line applies to both begin and end lines. This might be
intended. If you define an org-block-end-line face, it gets applied instead.
2) org-fontify-whole-block-delimiter-line is ignored. I'm aware I can
set the :extend t property to the face. If it does nothing, maybe this
variable should be removed.
3) The following block has no face applied.
- This only happens when the line with # at the top is empty
- The :height part of the face seems to be responsible
- It also works fine with default org version
4) If you go to the end of the fontified end_src line (first src
block), then press enter a couple of times the buffer position has the
org-block-begin-line face applied (move cursor to see it).
#
#+BEGIN_SRC elisp
auie
auriaest
#+END_SRC
Regards,
next reply other threads:[~2020-07-10 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 9:23 Sébastien Miquel [this message]
2020-07-10 11:46 ` Couple of issues with org block meta lines faces Kévin Le Gouguec
2020-07-14 10:19 ` Bug#42184: org-fontify-whole-*-line in emacs 27 (was: Couple of issues with org block meta lines faces) Kévin Le Gouguec
2020-08-02 21:23 ` Bug#42184: org-fontify-whole-*-line in emacs 27 Kévin Le Gouguec
2020-08-07 0:44 ` Kyle Meyer
2020-08-07 9:26 ` Kévin Le Gouguec
2020-08-09 4:43 ` Kyle Meyer
2020-08-09 14:12 ` Kévin Le Gouguec
2020-08-09 19:27 ` Kyle Meyer
2020-08-10 13:27 ` Kévin Le Gouguec
2020-08-11 0:43 ` 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=9fb38135-dc45-2d46-be0b-de9c297ac686@posteo.eu \
--to=sebastien.miquel@posteo.eu \
--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).