From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-exp-bibtex missing in git?
Date: Thu, 07 Mar 2013 23:46:06 +0100 [thread overview]
Message-ID: <87sj46bzgx.fsf@Rainer.invalid> (raw)
In-Reply-To: 871ubq50gq.fsf@bzg.ath.cx
Bastien writes:
> I'm all for following established standards, but I'm not sure what is
> the concrete proposal here.
I don't have one yet, mainly because I'm fuzzy on what direction this
will take. I ask again to consider what's already out there and that's
mainly BibTeX and things that work in principle like BibTex: in the
document itself you only say "here's a citation" and the rest of the
handling takes place outside (there are style files, databases in files
and online, tools for making and converting them). You make the
connection by specifying a configuration in the document. Now if Org
would abstract away some of these differences and maybe work in
conjunction with some of these outside programs to maybe pull references
from online sources and cache them locally (I always hate this step
since it is so repetitive), then we're talking.
> 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. In fact there is no reason to even think of it as a
file: protocol since the filename is just another parameter; you don't
want to get a file at all. Choose another more suitable protocol or, if
none exists, define your own. Assuming I interpret the intent of this
link correctly, you want to look up key in file my.bib and then
construct a citation with a post- and prenote, while (redundantly?)
using key again for display in the Org document. This is involving a
lot of things that don't necessarily belong into the same invocation:
where the data is stored, how to get at it, what parts of the data to
extract and lastly how to present the result. I submit that this is is
probably too complicated to try and cram all of this into the "link
syntax".
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2013-03-07 22:46 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 [this message]
2013-03-07 23:37 ` Rasmus Pank Roulund
2013-03-07 23:43 ` Rasmus
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=87sj46bzgx.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).