From: Joost Kremers <joostkremers@fastmail.fm>
To: emacs-orgmode@gnu.org
Subject: Re: [org-cite] citekey restrictions?
Date: Sun, 16 May 2021 20:49:27 +0200 [thread overview]
Message-ID: <87eee68p45.fsf@fastmail.fm> (raw)
In-Reply-To: <875yzizvm4.fsf@nicolasgoaziou.fr>
On Sun, May 16 2021, Nicolas Goaziou wrote:
> However, allowing anything means some keys will not be compatible with
> some bibliography formats. For example, I doubt BibTeX would appreciate
> a percent character in a key.
Careful, trying to find out the details of BibTeX's file format is a quest that
I think no-one has ever returned from. :D I have a comment in =parsebib.el=
saying that BibTeX allows $ ^ and & in entry keys, despite the fact that those
characters are special in TeX...
The regexp =parsebib.el= uses for entry keys is this:
"[^\"@\\#%',={} \t\n\f]+"
Mind you, I have no idea if BibTeX really rejects all these characters (well,
I'm pretty sure about the white space... :D ), but even if they are acceptable,
they probably don't occur much in the wild. At least I'm not aware of any user
complaints since the time I added support for $^&, which was four years ago,
> So... let's get liberal and say a key must match:
>
> (rx "@" (one-or-more (any word "-.:?!`'/*@+|()<>&_^$#%&~")))
>
> Nothing bad could happen, right?
On a scale of 1 to 10, 1 being getting an error message and having to go online
to find out what it means, and 10 being the total and utter destruction of our
solar system, I doubt it'll exceed 1.
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2021-05-16 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 10:12 [org-cite] citekey restrictions? Bruce D'Arcus
2021-05-16 11:29 ` Nicolas Goaziou
2021-05-16 11:41 ` Bruce D'Arcus
2021-05-16 12:55 ` Nicolas Goaziou
2021-05-16 13:10 ` Bruce D'Arcus
2021-05-16 18:49 ` Joost Kremers [this message]
2021-05-16 21:21 ` Nicolas Goaziou
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=87eee68p45.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=emacs-orgmode@gnu.org \
/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).