From: Ihor Radchenko <yantar92@gmail.com>
To: Hanspeter Gisler <hpgisleropen@bluewin.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Incorrect timestamp face in a heading if previous body contains link to such a heading [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Date: Tue, 12 Apr 2022 23:39:32 +0800 [thread overview]
Message-ID: <87v8ve9uq3.fsf@localhost> (raw)
In-Reply-To: <87k0bv74kh.fsf@hu.mail-host-address-is-not-set>
Hanspeter Gisler <hpgisleropen@bluewin.ch> writes:
> OBSERVED BEHAVIOR
> =================
>
> The following 2 files 'correct_face_rendering.org' and
> 'incorrect_face_rendering.org' render the 3rd headings timestamp face
> differently, once correctly and once incorrectly.
>
> incorrect_face_rendering.org
> ----------------------------
>
> * [2022-04-11 Mo] Heading 1 - referred to by some other heading's body
> :PROPERTIES:
> :ID: 9549d52f-439d-4011-ad72-9a9a7baad58b
> :END:
> * [2022-04-11 Mo] Heading 2 - referring to Heading 1
> Link to: [[id:9549d52f-439d-4011-ad72-9a9a7baad58b][[2022-04-11 Mo] Heading 1 - referred to by some other heading's body]]
> * [2022-04-11 Mo] Heading 3's timestamp face is incorrect
Confirmed.
This is yet another example (among many before) where our current
fontification engine is failing.
See https://orgmode.org/list/87ee7c9quk.fsf@localhost
The fix is WIP. Current version is at
https://github.com/yantar92/org/tree/feature/org-font-lock-element
Your example is fontified correctly in the WIP version :)
Best,
Ihor
prev parent reply other threads:[~2022-04-12 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 20:22 [BUG] Incorrect timestamp face in a heading if previous body contains link to such a heading [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)] Hanspeter Gisler
2022-04-12 15:39 ` Ihor Radchenko [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8ve9uq3.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hpgisleropen@bluewin.ch \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.