From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: org-exp-bibtex missing in git? Date: Thu, 07 Mar 2013 09:32:01 +0100 Message-ID: <871ubrr4ou.fsf@bzg.ath.cx> References: <20130303070635.GA12112@panahar> <87fw0cg42y.fsf@allisson.co> <87vc98be83.fsf@bzg.ath.cx> <87ehfwwgdd.fsf@gmail.com> <87ppzg2r05.fsf@med.uni-goettingen.de> <87ppzgusem.fsf@gmail.com> <87ppzcfy2e.fsf@med.uni-goettingen.de> <87lia0s7wi.fsf@bzg.ath.cx> <87obewe5jy.fsf@gmail.com> <87mwugqgt9.fsf@bzg.ath.cx> <87ip54drrn.fsf@med.uni-goettingen.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48884) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDWFC-0007TX-L6 for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 03:32:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UDWFB-0007Y9-Ir for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 03:32:06 -0500 Received: from mail-wg0-x22a.google.com ([2a00:1450:400c:c00::22a]:52669) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDWFB-0007Xy-5t for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 03:32:05 -0500 Received: by mail-wg0-f42.google.com with SMTP id 12so6053817wgh.3 for ; Thu, 07 Mar 2013 00:32:04 -0800 (PST) In-Reply-To: <87ip54drrn.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Thu, 07 Mar 2013 00:37:16 +0100") 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: Andreas Leha Cc: emacs-orgmode@gnu.org Hi Andreas, Andreas Leha writes: > But it looks very verbose to me. I expect the introduction to a > scientific paper (with typically many \cite{}s) to look disrupted. Each \cite{...} would be nothing more than [[cite:A.N.Whitehead][A.N.Whitehead]] in the Org file. The config happens in the #+LINK: cite ... line. I also think the proposal makes it easy to use several bibliographic files, with several #+LINK: citeN ... lines. In general, the idea is just to be able to hook an export function to a link after it has been expanded, and maybe this can be useful beyond this use-case. For example: #+LINK: local file://%s org-odt-local-link #+LINK: local file://%s org-odt-global-link The first line would be used for documents that you want to use locally, creating links to your files on your machine. The second line would be used for documents that want to share with others. -- Bastien