From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
Bruce D'Arcus <bdarcus@gmail.com>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: org-cite styles don't allow * in them
Date: Thu, 21 Apr 2022 10:06:06 +0200 [thread overview]
Message-ID: <87fsm6dfo1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87fsmp7cil.fsf@localhost> (Ihor Radchenko's message of "Thu, 07 Apr 2022 12:17:38 +0800")
Hello,
Ihor Radchenko <yantar92@gmail.com> writes:
> "Bruce D'Arcus" <bdarcus@gmail.com> writes:
>
>> On Sun, Apr 3, 2022 at 5:07 PM John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>>>
>>> I was looking into using latex commands as styles in org-cite, e.g.
>>>
>>> [cite/citet:@key]. That example works fine, but [cite/citet*:@key] is not allowed. Could that be allowed?
>>
>> I have no insight into the restriction, but I hope it can be removed.
>
> I do like the proposal in general, but I can see a potential issue for
> users. Constructs like "word*:" can be recognised as a valid bold
> emphasis ending. For example:
>
>>>> Some *bold emphasis with reference [cite/citet*:@key] will end
>>>> at "citet*", but not here*.
Note the issue already exists for italics and underline markers.
> Note that inserting zero-width space will not only be awkward here, but
> also breaks parser: e.g. [cite/cite<zwspace>t:@key] is not currently
> recognised as a citation.
I think the zero-width space can be inserted on the other side.
If there's no objection, I'll add asterisk character to the list of
allowed characters in citation style.
More generally, what other characters should be allowed ?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2022-04-21 8:48 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
2022-04-21 8:06 ` Nicolas Goaziou [this message]
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=87fsm6dfo1.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=yantar92@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 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).