From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: Citations, continued Date: Tue, 10 Feb 2015 07:03:43 -0800 Message-ID: References: <87vbjmn6wy.fsf@berkeley.edu> <87sieokx8e.fsf@berkeley.edu> <54d04780.cb58460a.5243.2603@mx.google.com> <87h9v3li8t.fsf@berkeley.edu> <54d078ff.b044440a.06ec.3cf6@mx.google.com> <87d25rkmag.fsf@berkeley.edu> <54d1bc7b.c57d440a.3c5d.2dca@mx.google.com> <87vbjh284z.fsf@nicolasgoaziou.fr> <87mw4tk4m7.fsf@berkeley.edu> <87oap7z664.fsf@nicolasgoaziou.fr> <87fvaibr3k.fsf@berkeley.edu> <87y4o9s5qc.fsf@nicolasgoaziou.fr> <87d25kpxap.fsf@pank.eu> <87k2zsso3w.fsf@nicolasgoaziou.fr> <87vbjcoewx.fsf@gmx.us> <87bnl4shqg.fsf@nicolasgoaziou.fr> <87h9uwwmgt.fsf@gmx.us> <87zj8oqqtz.fsf@nicolasgoaziou.fr> <87386eywus.fsf@nicolasgoaziou.fr> <87r3tydswi.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43163) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YLCM0-0006mc-4S for emacs-orgmode@gnu.org; Tue, 10 Feb 2015 10:03:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YLCLu-0008CC-U3 for emacs-orgmode@gnu.org; Tue, 10 Feb 2015 10:03:55 -0500 Received: from smtp.andrew.cmu.edu ([128.2.157.38]:39057) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YLCLu-0008Bv-Op for emacs-orgmode@gnu.org; Tue, 10 Feb 2015 10:03:50 -0500 In-reply-to: <87r3tydswi.fsf@gmx.us> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rasmus Cc: emacs-orgmode@gnu.org Rasmus writes: > Nicolas Goaziou writes: > >> Another option is to mimic custom links, if that's what you're thinkin= g >> of, which means to store every user-defined keyword in a variable and >> build a regexp out of it. I dislike it even more because the document = is >> not portable anymore, as it requires you to share your custom keywords. > > So, the (opinionated) useful defaults in biblatex are: > cite(s), parencite(s), footcite(s), texcite(s), fullcite, > footfullcite, nocite > > Citation types for extracting parts: > citeauthor, citetitle, citeyear, citedate, citeurl, If citenum was also in that list, then I agree. It is not that likely there is little need for custom style. > > From natbib: > citet (=3D=3D textcite), citep (=3D=3D parencite). > > Keys I don't care about, since they are quite biblatex specific: > smartcite, autocide, parentcite*, uppercase variants. *volcites(s) > (any objections?) None from me. > > In natbib: > citealt, citalp, starred variants > > So that's 17 support keys and two aliases. I guess this would deter mo= st > authors from needing custom styles. > >> Note that it rules out colons from KEY syntax (but we can use another >> less common character, e.g. "|"). > > The default bibtex.el style generates keys like "%A%y:%t", so I think "= :" > is no good, appealing as it is. > > =E2=80=94Rasmus > > > Footnotes: > =EF=BB=BF=C2=B9 which is just > [cite: common pre; pre1 @k1 post1; =E2=8B=AF; preN @kN postN; comm= on post] -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu