From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: org-exp-bibtex missing in git?
Date: Fri, 08 Mar 2013 00:43:12 +0100 [thread overview]
Message-ID: <877glikc8f.fsf@pank.eu> (raw)
In-Reply-To: <87sj46bzgx.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 07 Mar 2013 23:46:06 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
>> Do you mean using something like this
>>
>> [[file:my.bib&key=key;prenote=note1;postnote=note2][key]]
>>
>> for the file: protocol
>
> This is a prime example of how _not_ to do this, IMHO. The file
> protocol is an established protocol that you shouldn't bolt any extra
> parameters on.
I very much agree. The current "hacks" using links are annoying and
ugly, and if we were to do citations properly in Org—and I think we
should—it should NOT be using links (as Nicolas also pointed out).
It's a hack and shouldn't be made official.
In my book it would seem 'natural' to strive towards the following:
1. It should be Bibtex-based. I.e. Bibtex should be the 'database'
or storage for citation information. It may be stored in
Org-Bibtex-whatever, but Bibtex should be the natural base.
2. Citation selection should be possible via Reftex.
3. It should look nice in the buffer. For instance, with the
current link hacks I am shown the pre or post notes in place of
the citation. Ideally, it should be able to specify a
reftex-cite-format string on how to display stuff in the buffer.
Notes should be viewable in an non-disturbing way.
Ideally, I would want to see something like:
(POSTFIX, Jensen, 1906, SUFFIX)
or
Jensen (POSTFIX, 1906, SUFFIX)
(If my memory serves me correctly this is how BibLatex places
notes).
(4. If we are to adopt LaTeX terminology we should adopt the
terminology of BibLatex as opposed to Natbib).
–Rasmus
--
May the Force be with you
next prev parent reply other threads:[~2013-03-07 23:43 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 7:06 org-exp-bibtex missing in git? Vikas Rawal
2013-03-03 10:39 ` François Allisson
2013-03-03 17:11 ` Bastien
2013-03-03 17:19 ` Nicolas Goaziou
2013-03-03 20:00 ` Andreas Leha
2013-03-03 20:42 ` Nicolas Goaziou
2013-03-04 9:29 ` Eric S Fraga
2013-03-06 13:38 ` Andreas Leha
2013-03-06 18:25 ` Bastien
2013-03-06 18:39 ` Nicolas Goaziou
2013-03-06 21:16 ` Andreas Leha
2013-03-06 22:55 ` Bastien
2013-03-06 23:37 ` Andreas Leha
2013-03-07 8:32 ` Bastien
2013-03-07 8:44 ` Andreas Leha
2013-03-07 5:38 ` aaronecay
2013-03-07 8:54 ` Eric S Fraga
2013-03-07 10:21 ` Bastien
2013-03-07 11:04 ` Aaron Ecay
2013-03-07 11:16 ` Bastien
2013-03-07 12:03 ` Aaron Ecay
2013-03-07 13:13 ` Nicolas Goaziou
2013-03-07 15:28 ` Bastien
2013-03-07 17:39 ` Achim Gratz
2013-03-07 22:06 ` Bastien
2013-03-07 22:46 ` Achim Gratz
2013-03-07 23:37 ` Rasmus Pank Roulund
2013-03-07 23:43 ` Rasmus [this message]
2013-03-08 0:10 ` Thomas S. Dye
2013-03-08 9:27 ` Rasmus
2013-03-08 17:36 ` Thomas S. Dye
2013-03-08 19:32 ` aaronecay
2013-03-08 19:40 ` Rasmus
2013-03-08 19:29 ` aaronecay
2013-03-09 9:28 ` Bastien
2013-03-19 5:02 ` Aaron Ecay
2013-04-18 10:58 ` Bastien
2013-03-09 15:15 ` Nicolas Goaziou
2013-03-09 16:04 ` Jambunathan K
2013-03-09 16:12 ` Jambunathan K
2013-03-09 17:08 ` Thomas S. Dye
2013-03-07 10:04 ` Jambunathan K
2013-03-11 13:34 ` Andreas Leha
2013-03-04 4:40 ` Vikas Rawal
2013-03-04 13:55 ` Suvayu Ali
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=877glikc8f.fsf@pank.eu \
--to=rasmus@gmx.us \
--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).