From: Michael Klooss <michael.klooss@aalto.fi>
To: emacs-orgmode@gnu.org
Subject: [BUG] org-highlight-latex-and-related naive + script renders links improperly
Date: Sat, 20 Jan 2024 23:09:39 +0200 [thread overview]
Message-ID: <36d11398-a259-4ec5-8f2f-3c4c064216db@aalto.fi> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1293 bytes --]
Hello,
I have encountered following bug when I set =native= and =script= in
=org-highlight-latex-and-related=:
Expected behaviour: Links are displayed as before.
Actual behaviour: If a link contains an underscore (which is quite
common), then a "subscript" is displayed as part of the link.
Example: The link
[[https://en.wikipedia.org/wiki/Harmonic_series_(mathematics)][Text]]
is rendered as
_seriesLinkb
with a small "s", and "_series" and "Text" fontified differently, but
all of it is still recognized as the link (e.g., highlighted and
clickable on mouseover).
Tested on Debian Testing with emacs -Q where:
Emacs : GNU Emacs 29.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.38, cairo version 1.16.0)
of 2023-08-30, modified by Debian
Package: Org mode version 9.6.6 (release_9.6.6 @
/usr/share/emacs/29.1/lisp/org/)
Additional info:
The bug does not seem to occur when =latex= and =script= is used (but
=native= looks better, so I would like to keep it).
Considering the much improved readability
=org-highlight-latex-and-related= gives for documents with latex mixed
in, the malformed link rendering is not a major problem, but confusing
nonetheless. So it would be nice if this could be fixed.
Thank you and best,
Michael
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 669 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next reply other threads:[~2024-01-30 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 21:09 Michael Klooss [this message]
2024-01-30 14:12 ` [BUG] org-highlight-latex-and-related naive + script renders links improperly Ihor Radchenko
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=36d11398-a259-4ec5-8f2f-3c4c064216db@aalto.fi \
--to=michael.klooss@aalto.fi \
--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 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.