emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: aaronecay@gmail.com,
	Andreas Leha <andreas.leha@med.uni-goettingen.de>,
	emacs-orgmode@gnu.org
Subject: Re: org-exp-bibtex missing in git?
Date: Thu, 07 Mar 2013 14:13:27 +0100	[thread overview]
Message-ID: <87boavcpzc.fsf@gmail.com> (raw)
In-Reply-To: <87wqtjo6h6.fsf@bzg.ath.cx> (Bastien's message of "Thu, 07 Mar 2013 11:21:41 +0100")

Bastien <bzg@altern.org> writes:

> 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?

I think that if we ever implement a bibliography/citations handlers,
they should be first class objects in Org syntax (like footnotes).
Overloading link syntax would, IMO, be wrong in that case.

Also, link abbrevs and link protocol handlers are meant for the
end-user, not for official syntax.

I suggest to avoid using link syntax for citations altogether, but if we
do, the citation must not depend on an user-defined function. The whole
syntax must be attached to the link.

Therefore, I agree that link syntax needs to be extended. I'm thinking
in particular about per-link export properties. Adding in separator in
the path part is an interesting idea, as long as it isn't a string
widely used in paths.

In a nutshell, my POV is:
 - we should avoid overloading #+LINK syntax and overusing link-abbrevs.
 - citations, if implemented globally, deserve their own syntax.
 - changing the general link type to:

     [[PROTOCOL:PATH/SEP/OPTIONS][DESCRIPTION]]

   is fine.

 
Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2013-03-07 13:13 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 [this message]
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=87boavcpzc.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=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).