From: Ihor Radchenko <yantar92@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, emacs-orgmode@gnu.org
Subject: Re: Bug: PDF Export of Link fails [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)]
Date: Fri, 03 Sep 2021 17:18:02 +0800 [thread overview]
Message-ID: <87mtouuiet.fsf@localhost> (raw)
In-Reply-To: <87v93im57e.fsf@gmail.com>
Timothy <tecosaur@gmail.com> writes:
> Causes issues. I also note that in the Org-mode buffer the comma seems to cause
> issues. I’ve attached a screenshot, in which you can see in the “comma, italics”
> situation:
> ⁃ The second line is not italic
> ⁃ The second `/' of the pair is shown (and I have Org’s entity hiding setting enabled)
The problem is with org-emph-re.
Our second component of org-emphasis-regexp-components is
> Chars allowed as postmatch. End of line will be allowed too.
"-[:space:].,:!?;'\")}\\["
So, org-element-italic-parser will treat /, sequence as end of the
italic text disregarding that /, is part of the link.
If you try the following text, it will not export correctly as well:
/Beginning is italic 1^{/,} and tail should be italic/
Though fontification somehow works.
Or we can put some other allowed object like inline src block:
/Beginning is italic src_elisp{(message "Foo/,")} and tail should be italic/
This time both export and fontification do not work.
I suspect that we need to upgrade org-element-italic-parser in
non-trivial way to fix this.
Best,
Ihor
next prev parent reply other threads:[~2021-09-03 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 5:17 Bug: PDF Export of Link fails [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)] Dr. Arne Babenhauserheide
2021-09-03 8:24 ` Timothy
2021-09-03 9:18 ` Ihor Radchenko [this message]
2021-09-03 8:30 ` Timothy
2021-09-03 14:18 ` Bug: PDF Export of Link fails (emphasis ends inside link target) Maxim Nikulin
2021-09-03 14:33 ` Timothy
2021-09-03 14:57 ` Maxim Nikulin
2021-09-19 12:11 ` Max Nikulin
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=87mtouuiet.fsf@localhost \
--to=yantar92@gmail.com \
--cc=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@gmail.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 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.