From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Citation syntax: Underscore MUST(?) be allowed in cite keys?
Date: Mon, 09 Mar 2015 17:36:37 -0700 [thread overview]
Message-ID: <871tkxzo16.fsf@berkeley.edu> (raw)
In-Reply-To: <871tkyxgjg.fsf@ucl.ac.uk>
Hi Eric and all,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Monday, 9 Mar 2015 at 09:05, Richard Lawrence wrote:
>
>> Another option would be to allow clause-ending punctuation in all keys,
>> but introduce some kind of optional syntax to express `this key ends
>
> No, please no! I would say that the majority of my citations are at the
> end of sentences... I would end up having to use this additional syntax
> frequently. I'd rather use syntax to disambiguate the less frequent
> cases and keys with punctuation are those (for me, at least).
I feel the same as you do about this, so here's one more thought for the
thread. How about this alternative?
We keep the existing syntax for keys, which disallows key-ending
punctuation, but we also allow a second style of key, in which curly
braces surround the key name proper, like:
@{Doe1999}
Then we can conceivably allow any character at all between the braces,
including punctuation (except `}', which is also a restriction on LaTeX
keys). That means this type of key should be able to accommodate just
about anything the future may bring.
The opening `{' immediately after the `@' will make this type of key
easy for the parser to distinguish from the first type, and the closing
`}' makes the end of the key unambiguous with respect to following
punctuation.
Tools that insert keys from citation managers can check whether a key
respects the brace-less syntax, and offer to insert it using the second
style when it doesn't. Or they could be configured to always use this
style, if the user prefers.
And anyone who doesn't need to disambiguate keys from punctuation can
use the brace-less style, which (in my opinion) is easier to read and
type.
What do people think?
Best,
Richard
next prev parent reply other threads:[~2015-03-10 0:37 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 18:21 Citation syntax: Underscore MUST(?) be allowed in cite keys? Vaidheeswaran C
2015-03-04 18:30 ` Rasmus
2015-03-04 18:42 ` Vaidheeswaran C
2015-03-04 19:01 ` Rasmus
2015-03-04 19:18 ` Vaidheeswaran C
2015-03-04 21:38 ` Christian Moe
2015-03-05 5:00 ` Richard Lawrence
2015-03-06 10:49 ` Nicolas Goaziou
2015-03-06 11:55 ` Rasmus
2015-03-06 17:34 ` Nicolas Goaziou
2015-03-06 17:55 ` Rasmus
2015-03-06 21:01 ` Eric S Fraga
2015-03-06 12:41 ` Vaidheeswaran C
2015-03-06 18:09 ` Richard Lawrence
2015-03-07 6:28 ` Vaidheeswaran C
2015-03-07 17:09 ` Richard Lawrence
2015-03-07 18:20 ` Vaidheeswaran C
2015-03-08 8:19 ` Stefan Nobis
2015-03-07 17:50 ` Thomas S. Dye
2015-03-08 0:18 ` Nicolas Goaziou
2015-03-08 2:12 ` Rasmus
2015-03-08 4:19 ` Thomas S. Dye
2015-03-08 12:34 ` Rasmus
2015-03-08 17:07 ` Thomas S. Dye
2015-03-08 17:49 ` Rasmus
2015-03-09 1:56 ` Richard Lawrence
2015-03-09 2:29 ` Thomas S. Dye
2015-03-09 8:57 ` Stefan Nobis
2015-03-09 9:19 ` Vaidheeswaran C
2015-03-09 9:49 ` Stefan Nobis
2015-03-09 10:46 ` Vaidheeswaran C
2015-03-09 11:02 ` Rasmus
2015-03-09 11:27 ` Stefan Nobis
2015-03-09 16:05 ` Richard Lawrence
2015-03-09 16:37 ` Thomas S. Dye
2015-03-09 16:49 ` Eric S Fraga
2015-03-09 17:49 ` Thomas S. Dye
2015-03-09 18:00 ` Eric S Fraga
2015-03-09 18:44 ` Thomas S. Dye
2015-03-09 19:26 ` Eric S Fraga
2015-03-09 18:50 ` Richard Lawrence
2015-03-09 21:07 ` Rasmus
2015-03-09 22:33 ` Richard Lawrence
2015-03-10 0:37 ` Rasmus
2015-03-10 15:35 ` Richard Lawrence
2015-03-10 0:36 ` Richard Lawrence [this message]
2015-03-10 7:06 ` Eric S Fraga
2015-03-10 8:15 ` Nicolas Goaziou
2015-03-10 8:50 ` Rasmus
2015-03-10 10:18 ` Eric S Fraga
2015-03-10 14:35 ` Matt Price
2015-03-10 15:32 ` Richard Lawrence
-- strict thread matches above, loose matches on Subject: below --
2015-03-04 18:21 Vaidheeswaran C
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=871tkxzo16.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).