emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Tim Loderhose <tim@loderhose.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Erroneous link highlighting in src blocks (9.5.5-geeae6e)
Date: Sun, 09 Oct 2022 11:48:55 +0800	[thread overview]
Message-ID: <877d19fyhk.fsf@localhost> (raw)
In-Reply-To: <XdWFnN3XCJ67x3SvoiVo_itGGYfboKmuWp7OxQxRZ_SGA5vgb72oWBoqTmOUUtiqUR890-kIXjI7uhlse-HFYqNVJTyVlc15zAzbP8qHVdo=@loderhose.com>

Tim Loderhose <tim@loderhose.com> writes:

> Hi,
>
> In recent org, org-highlight-links including 'bracket' will hide content
> with double brackets inside src blocks.
> A vanilla config loading 9.5.5 org (I did this through straight.el) can reproduce this with a
> minimal org file including just:
>
> #+begin_src python
> [[a]]
> #+end_src
>
> The brackets will be hidden.

Thanks for reporting!

This is related to the new folding engine that broke the brittle balance
of current regexp-based Org fontification.

In general, fontification issues are numerous in Org and have to be
fixed by a complete rewrite of our fontification system. See
https://orgmode.org/list/87ee7c9quk.fsf@localhost

However, in a view of upcoming Org release, I am going to fix this
particular issue now. It is not too difficult.

Fixed on main now.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=41a409f79d07fe7a3e8c5f934b97e4a2884bf948

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2022-10-09  3:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 15:46 [BUG] Erroneous link highlighting in src blocks (9.5.5-geeae6e) Tim Loderhose
2022-10-09  3:48 ` 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

  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=877d19fyhk.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tim@loderhose.com \
    /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).