From: Ihor Radchenko <yantar92@gmail.com>
To: Bruce D'Arcus <bdarcus@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: org-cite styles don't allow * in them
Date: Tue, 19 Apr 2022 10:59:08 +0800 [thread overview]
Message-ID: <87a6chpymb.fsf@localhost> (raw)
In-Reply-To: <CAF-FPGODEyok=tBWH4NEXoqqSZYmd8Jbpzmw0Z+83zp594jD7w@mail.gmail.com>
"Bruce D'Arcus" <bdarcus@gmail.com> writes:
> Just to clarify, I don't believe the discussion is to add such styles to
> the included org-cite processors (which already support such
> functionality), but rather to allow it, for example for third party ones;
> say a hypothetical org-ref one.
Sure. However, the discussed problem should be supported by Org core one
way or another.
Consider a third-party processor that introduces citet* style.
Then, some user happens to encounter the discussed edge case with
*bold [cite:citet*:@key}
If the third-party processor does not also have citet*/ variant, what
can the user do? Be stuck?
From Org's point of view, we listed 2 possible approaches:
1. Allow unicode ⋆ star in citation styles
2. Allow ordinary * star in citation styles + Make oc.el recognise
style* as an alias to style*/ + make org-lint warn about the edge
case.
Best,
Ihor
next prev parent reply other threads:[~2022-04-19 2:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 21:06 org-cite styles don't allow * in them John Kitchin
2022-04-05 15:56 ` Bruce D'Arcus
2022-04-05 16:11 ` John Kitchin
2022-04-05 17:41 ` Bruce D'Arcus
2022-04-07 4:17 ` Ihor Radchenko
2022-04-07 11:30 ` John Kitchin
2022-04-16 16:29 ` Bruce D'Arcus
2022-04-17 8:42 ` Ihor Radchenko
2022-04-17 12:14 ` John Kitchin
2022-04-17 13:18 ` Ihor Radchenko
2022-04-17 14:24 ` John Kitchin
2022-04-18 9:09 ` Ihor Radchenko
2022-04-18 10:25 ` Bruce D'Arcus
2022-04-19 2:59 ` Ihor Radchenko [this message]
2022-04-21 8:06 ` Nicolas Goaziou
2022-04-21 10:09 ` Ihor Radchenko
2022-04-21 11:28 ` Nicolas Goaziou
2022-04-21 13:40 ` Ihor Radchenko
2022-04-22 12:42 ` Bruce D'Arcus
2022-04-22 13:30 ` John Kitchin
2022-05-22 15:51 ` Bruce D'Arcus
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=87a6chpymb.fsf@localhost \
--to=yantar92@gmail.com \
--cc=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).