From: Nicolas Goaziou <email@example.com>
To: Timothy <firstname.lastname@example.org>
Cc: emacs-orgmode <email@example.com>
Subject: Re: Formal syntax for org-cite
Date: Wed, 01 Dec 2021 14:16:34 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Timothy's message of "Wed, 01 Dec 2021 01:21:30 +0800")
Timothy <firstname.lastname@example.org> writes:
> Looking at https://orgmode.org/worg/dev/org-syntax.html, there isn't,
Yup, I forgot to update it.
> I have not yet confirmed what =KEYPREFIX= and =KEYSUFFIX= may contain,
> but as a starting point, any of the characters allowed in =KEY= except
> =@= plus whitespace would seem fairly safe. =KEYSUFFIX= must start with
> a whitespace character to be able to be differentiated from =KEY=.
KEYPREFIX may not contain a semicolon nor any combination forming a key
(at-sign followed by a word character or some symbols). Square brackets
are allowed only if they form a symmetric pair. Any other character is
KEYSUFFIX has the same restrictions, minus the limitation about the key.
> =CITESTYLE= consists of a main =STYLE= and any number of =VARIANT=s
> (including zero), prefixed by forwards slashes in the following pattern
Nope. This is only /STYLE/VARIANT, however VARIANT can contain "/" character.
> =STYLE= and =VARIANT= can be made of any alphanumeric character, =_=, or =-=.
> =GLOBALPREFIX= and =GLOBALSUFFIX= can contain the same characters as
> =KEYPREFIX= and =KEYSUFFIX=, however =GLOBALPREFIX= must end with a
> semicolon, and =GLOBALSUFFIX= must start with a semicolon.
Note the semicolons do not belong to affixes.
> "cite" and =CITESTYLE=, =KEYCITES= and =GLOBALSUFFIX= are /not/
> separated by whitespace. Neither are =KEYPREFIX=, =@KEY=, or =KEYSUFFIX=
> separated by whitespace.
Addendum: whitespaces are not significant after the leading colon, and
before the closing square bracket. They are significant in any other
next prev parent reply other threads:[~2021-12-01 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 17:21 Formal syntax for org-cite Timothy
2021-11-30 23:24 ` Tom Gillespie
2021-12-01 13:16 ` Nicolas Goaziou [this message]
2021-12-02 6:26 ` Timothy
2021-12-02 12:13 ` Timothy
2021-12-02 12:50 ` Ihor Radchenko
2021-12-02 12:55 ` Timothy
2021-12-30 8:27 ` Timothy
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).