From: Bastien <bzg@altern.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
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 16:28:46 +0100 [thread overview]
Message-ID: <87fw075ivl.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87boavcpzc.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 07 Mar 2013 14:13:27 +0100")
Hi Nicolas,
I like Aaron's idea (maybe others proposed this too) of having
parameters in links:
[[file:my.bib::key&&prenote=my prenote&&postnote=my postnote]]
[[http://perdu.com&&title=You're lost?]]
This is orthogonal to my proposal of extending #+LINK to be able
to define new protocols (by allowing to add a follow and an export
functions); and this is orthogonal to whether link abbrevs can have
more than one formatting string %s.
We would just need to pass the parameters as keywords to the export
function, either the default one, either the defined by the protocol.
E.g., the first link would be represented by the parser like this:
(:type "file"
:path "my.bib"
:raw-link "file:orgmode.org::test2"
:application nil
:search-option "test2"
:parameters '(:title "You're lost")
:begin 63
:end 97
:contents-begin 90
:contents-end 95
:post-blank 0
:parent #3)
Then org-html-link would get the parameters with
(org-element-property :parameters link)
=> '(:title "You're lost")
I think this is general and useful.
If we implement this, it would be nice to extend link abbrevs to
support multiple formatters in `org-link-abbrev-alist'.
#+LINK: citeA file:my.bib::%s&&prenote=%s&&postnote=%s
And this would spare us for the need of another object dedicated
to bibliographic citations:
[[citeA::key&&prenote=my note&&postnote=my note]]
What do you think?
--
Bastien
next prev parent reply other threads:[~2013-03-07 15:29 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
2013-03-07 15:28 ` Bastien [this message]
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=87fw075ivl.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=aaronecay@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).