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 12:16:39 +0100 Message-ID: <876213laso.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> <87wqtjo6h6.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34307) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDYog-0000pD-1t for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 06:16:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UDYoa-0004YS-Th for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 06:16:53 -0500 Received: from mail-wg0-f46.google.com ([74.125.82.46]:57217) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDYoa-0004YH-Mr for emacs-orgmode@gnu.org; Thu, 07 Mar 2013 06:16:48 -0500 Received: by mail-wg0-f46.google.com with SMTP id fg15so544196wgb.13 for ; Thu, 07 Mar 2013 03:16:48 -0800 (PST) In-Reply-To: (Aaron Ecay's message of "Thu, 7 Mar 2013 06:04:28 -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: Aaron Ecay Cc: Andreas Leha , emacs-orgmode@gnu.org Hi Aaron, Aaron Ecay writes: > I suspect you may be targeting the wrong layer. Don't we want to use > org-link-protocols, not org-link-abbrev-alist? Protocols are already > handled by the exporter, so there should be no need for a change like > this one: > [...] I want to allow adding link protocols (what I called "adding link types") from #+LINK. >> 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? > > My proposal works without any changes to the exporter's structure > (except adding the #+BIBLIOGRAPHY keyword, which is a one-line > emendation). It does not allow the equivalent of your "#+LINK: > bib:%s;%s;%s" for specifying the pre/post delimiters, but maybe it > would be better from a standardization-of-syntax point of view to have > just one way of encoding them? IIUC your proposal introduces some syntactic glue here: [[type:key;pre;post][desc]] ^ ^ If we allow this, it's better to allow this in general than just for a specific link type. Hence my proposal to extend link abbreviation to be recognized as new link types when the #+LINK line contains more than two strings. See for example this new link type (or "protocol"): #+LINK: with-title::%s http://orgmode.org/worg/doc.html# nil org-html-link-with-title [[with-title::org-mode::A link title][org-mode]] org-html-link-with-title would then take care of exporting this as a link like org-mode. There are really two changes here: 1. extending #+LINK so that the third and fourth strings are recognized as follow and export functions 2. extending #+LINK so that a formatting string in the link abbreviation name is handle later on by those functions. What do you think? -- Bastien