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 11:21:41 +0100 Message-ID: <87wqtjo6h6.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> <876213lqfk.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:49178) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDXxM-00022w-33 for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 05:21:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UDXxK-0003PK-59 for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 05:21:48 -0500 Received: from mail-bk0-x22a.google.com ([2a00:1450:4008:c01::22a]:33080) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDXxJ-0003Or-Tu for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 05:21:46 -0500 Received: by mail-bk0-f42.google.com with SMTP id jk7so136430bkc.15 for ; Thu, 07 Mar 2013 02:21:45 -0800 (PST) In-Reply-To: <876213lqfk.fsf@gmail.com> (aaronecay@gmail.com's message of "Thu, 07 Mar 2013 00:38:55 -0500") 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: aaronecay@gmail.com Cc: Andreas Leha , emacs-orgmode@gnu.org Hi Aaron, I now see where you and Eric go and this is good! Here is a revised suggestion, allowing to add link types from withing the #+LINK keyword. 1. Allow more syntax for #+LINK: #+LINK: bib;%s;%s file:my.bib::%s org-bib-follow-link org-bib-export-link If `org-bib-follow-link' is nil, it'll follow [[bib:my.bib::key][key]] like it does right now, jumping to the "key" line in the my.bib file. If `org-bib-follow-link' is non-nil, it will operate on [[bib:my.bib::key;prenote;postnote][key]] and find the correct key. If `org-bib-export-link' is non-nil, it will operate on [[bib:my.bib::key;prenote;postnote][key]] and export it correctly depending on the backend. The change required for the exporter is to let `org-bib-follow-link' and `org-bib-export-link' operate on [[bib::my.bib::key;prenote;postnote]], not on the expanded link. IOW, link expansion should happen within the backend export routines, treating abbreviated links with formatting strings (aka "bib;%s;%s") in a special way. I see two advantages: - adding new types will be easier -- e.g.: #+LINK: cite file:my.bib::%s org-bib-follow-link org-bib-export-link - users can decide what syntactic glue they want to their abbreviated links (using ";" or another separator). Nicolas, do you think it is feasible/good to delay link expansion till the backend knows whether the abbreviated link is associated to follow/export function that would understand formatting strings in the abbreviated form? -- Bastien