From: Kyle Meyer <kyle@kyleam.com>
To: Junwei Wang <junwei.wang@cryptoexperts.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Orgmode export takes "AC:" as a link keyword [9.5 (nil @ /Users/junwei/.emacs.d/.local/straight/build-27.1/org-mode/)]
Date: Sun, 13 Dec 2020 06:05:07 GMT [thread overview]
Message-ID: <87h7oqutpq.fsf@kyleam.com> (raw)
In-Reply-To: <f9bcaaed-0acc-ce11-d9c3-a657dfc647af@cryptoexperts.com>
Junwei Wang writes:
> When exporting orgmode file into HTML file, the exporter "mistakely"
> consider "AC:" as some keyword for linking and the string following
> "AC:" would be something link to.
It looks like org-ref is setting up these links for you. Here's the
relevant bit from the configuration you included:
org-link-parameters '([...]
("Ac" :follow or-follow-acronym :face org-ref-acronym-face :help-echo
or-acronym-tooltip :export
#[771 "\211\301>\203\302\303\300A#\207\302\304\226\"\207"
[("Ac" . "Gls") (latex beamer) format "\\%s{%s}" "%s"] 7
"\n\n(fn PATH _ FORMAT)"]
)
("ac" :follow or-follow-acronym :face org-ref-acronym-face :help-echo
or-acronym-tooltip :export
#[771 "\211\301>\203\302\303\300A#\207\302\304\226\"\207"
[("ac" . "gls") (latex beamer) format "\\%s{%s}" "%s"] 7
"\n\n(fn PATH _ FORMAT)"]
[...]
I suspect the uppercase "AC" being treated as a link despite it not
appearing in org-link-parameters is a case-related bug somewhere in
Org's link handling. While that's worth looking into, it just shifts
things as far as your original example is concerned: replace "AC" with
"ac", and you have the same issue that you reported.
One way to make Org not treat "ac:foo" as a link is to insert a
zero-width space (with, e.g., <C-x 8 RET 200B>) between "ac" and ":".
(info "(org)Escape Character")
next prev parent reply other threads:[~2020-12-13 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 17:21 Bug: Orgmode export takes "AC:" as a link keyword [9.5 (nil @ /Users/junwei/.emacs.d/.local/straight/build-27.1/org-mode/)] Junwei Wang
2020-12-13 6:05 ` Kyle Meyer [this message]
2020-12-13 17:24 ` Junwei Wang
2020-12-16 6:00 ` 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=87h7oqutpq.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=junwei.wang@cryptoexperts.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).