From: Aaron Ecay <aaronecay@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>, emacs-orgmode@gnu.org
Subject: Re: org-exp-bibtex missing in git?
Date: Thu, 7 Mar 2013 06:04:28 -0500 [thread overview]
Message-ID: <CAFcZrT0gHAEvBTcH9i3fz3KqNdUj5=m0jqKnGM_-hBs95VHdQg@mail.gmail.com> (raw)
In-Reply-To: <87wqtjo6h6.fsf@bzg.ath.cx>
Hi Bastien,
On Thu, Mar 7, 2013 at 5:21 AM, Bastien <bzg@altern.org> wrote:
> 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.
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:
[...]
> 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?
Aaron
next prev parent reply other threads:[~2013-03-07 11:04 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 [this message]
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
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='CAFcZrT0gHAEvBTcH9i3fz3KqNdUj5=m0jqKnGM_-hBs95VHdQg@mail.gmail.com' \
--to=aaronecay@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=bzg@altern.org \
--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).