Hi Aaron,
Aaron Ecay aarone...@gmail.com writes:
I hope this is not bothersome
... it is not, heads up are always welcome.
but have you had a chance to look at these patches?
No -- and we are close to the release now, so let's not introduce
new syntax for this. We still need to discuss
Hi Bastien,
2013ko martxoak 9an, Bastien-ek idatzi zuen:
This is great -- I'll be offline this week-end, so I won't have time
to have a careful look before monday. But I will.
I hope this is not bothersome, but have you had a chance to look at
these patches?
I thought they would solve the
Jambunathan K kjambunat...@gmail.com writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
\footfullcite[prenote][postnote]{key}
What would prenote and postnote typically contain. Where would they
appear in the exported document - In the citation reference or in the
citation
Hi Aaron,
aarone...@gmail.com writes:
This is now implemented, in the first of three patches attached to this
email. The second patch is a reworked version of the bibliography
support in my last patch, and the third implements link attributes for
HTML links.
This is great -- I'll be
Hello,
aarone...@gmail.com writes:
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.
Do you have a proposal for how this syntax would look? You
Nicolas Goaziou n.goaz...@gmail.com writes:
I favor [cite:PROPERTIES] over [[cite:PROPERTIES]], because the latter
(link syntax) implies a (optional) description part. I don't think
a description is ever meaningful in citations.
I have been holding on to this for a while. Just typing it out
Jambunathan K kjambunat...@gmail.com writes:
Citation processor could be whatever org-exp-bibtex interfaces with
right now. I also have some proof-of-concept - see zotcite - for
zotero.
I have a proof-of-concept on how to use Jabref to get citations in to
ODT export. I will share a recipe
Jambunathan K kjambunat...@gmail.com writes:
I am not clear about:
1. How multiple keys are to be handled.
2. What prenotes or postnotes mean.
3. Chicago note style etc.
I think the community should answer and articulate 1, 2, 3 clearly.
With my proposal, there could be some minor
Aloha Rasmus,
Rasmus ras...@gmx.us writes:
t...@tsdye.com (Thomas S. Dye) writes:
Indeed, but perhaps there is a better possible syntax. With Reftex
the the link-way is OK, but I still think that we should think about
whether there is a Better Wayᵀᴹ if Org was to add it officially.
Hello Bastien (et al),
2013ko martxoak 7an, Bastien-ek idatzi zuen:
Hi Nicolas,
I like Aaron's idea (maybe others proposed this too) of having
parameters in links:
[[file:my.bib::keyprenote=my prenotepostnote=my postnote]]
[[http://perdu.comtitle=You're lost?]]
This is orthogonal
Hi Rasmus,
2013ko martxoak 7an, Rasmus Pank Roulund-ek idatzi zuen:
In my book it would seem 'natural' to strive towards the following:
1. It should be Bibtex-based. I.e. Bibtex should be the 'database'
or storage for citation information. It may be stored in
Aaron,
2. Citation selection should be possible via Reftex.
In principle this is true, but I think RefTeX is deeply intertwined with
the assumption that it is running in a LaTeX buffer. Going through its
code and making it major-mode-agnostic is a worthy project all of its
own. But it
Hi Andreas,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
But it looks very verbose to me. I expect the introduction to a
scientific paper (with typically many \cite{}s) to look disrupted.
Each \cite{...} would be nothing more than
[[cite:A.N.Whitehead][A.N.Whitehead]] in the Org
Hi Bastien,
Bastien b...@altern.org writes:
Hi Andreas,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
But it looks very verbose to me. I expect the introduction to a
scientific paper (with typically many \cite{}s) to look disrupted.
Each \cite{...} would be nothing more than
aarone...@gmail.com writes:
[...]
I’ve got some mostly-working code that exports citations, only for
latex, using a different approach (similar to Eric’s). I’ve cleaned it
up some, and attached it as a patch to this email.
This looks quite nice.
I am unlikely to try it out, however, as my
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
\footfullcite[prenote][postnote]{key}
What would prenote and postnote typically contain. Where would they
appear in the exported document - In the citation reference or in the
citation definition. Can the same key have different pre-note
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
Hi Bastien,
On Thu, Mar 7, 2013 at 5:21 AM, Bastien b...@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
Hi Aaron,
Aaron Ecay aarone...@gmail.com 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
Hi Bastien,
On Thu, Mar 7, 2013 at 6:16 AM, Bastien b...@altern.org wrote:
I want to allow adding link protocols (what I called adding link
types) from #+LINK.
Hmm. I think I am beginning to understand your motivation for this.
IIUC your proposal introduces some syntactic glue here:
Bastien b...@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
Hi Nicolas,
I like Aaron's idea (maybe others proposed this too) of having
parameters in links:
[[file:my.bib::keyprenote=my prenotepostnote=my postnote]]
[[http://perdu.comtitle=You're lost?]]
This is orthogonal to my proposal of extending #+LINK to be able
to define new protocols (by
Bastien writes:
I like Aaron's idea (maybe others proposed this too) of having
parameters in links:
We've had some of this discussion about two years ago IIRC, so here I am
again: there's an internet standard for this kind of thing, it's called
URN/URI. If we adhere to this, we can at least
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Bastien writes:
I like Aaron's idea (maybe others proposed this too) of having
parameters in links:
We've had some of this discussion about two years ago IIRC, so here I am
again: there's an internet standard for this kind of thing, it's
Bastien writes:
I'm all for following established standards, but I'm not sure what is
the concrete proposal here.
I don't have one yet, mainly because I'm fuzzy on what direction this
will take. I ask again to consider what's already out there and that's
mainly BibTeX and things that work in
Achim Gratz strom...@nexgo.de writes:
Do you mean using something like this
[[file:my.bibkey=key;prenote=note1;postnote=note2][key]]
for the file: protocol
This is a prime example of how _not_ to do this, IMHO. The file
protocol is an established protocol that you shouldn't bolt any
Rasmus ras...@gmx.us writes:
Achim Gratz strom...@nexgo.de writes:
Do you mean using something like this
[[file:my.bibkey=key;prenote=note1;postnote=note2][key]]
for the file: protocol
This is a prime example of how _not_ to do this, IMHO. The file
protocol is an established
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.orgmode as well.
Achim Gratz strom...@nexgo.de writes:
Do you mean using something like this
[[file:my.bibkey=key;prenote=note1;postnote=note2][key]]
for the file: protocol
This is a prime example
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@altern.org writes:
Hi Vikas,
François Allisson franc...@allisson.co writes:
org-exp-bibtex, because of its dependency on
Hi Andreas and all,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Eric suggested/uses this format (thanks for sharing, Eric):
[[cite:jones-etal-2000][Jones et al., 2000]]
^^^ ^^
key displayed in org
I'd suggest to
Hello,
Bastien b...@altern.org writes:
Hi Andreas and all,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Eric suggested/uses this format (thanks for sharing, Eric):
[[cite:jones-etal-2000][Jones et al., 2000]]
^^^ ^^
key
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Bastien b...@altern.org writes:
Hi Andreas and all,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Eric suggested/uses this format (thanks for sharing, Eric):
[[cite:jones-etal-2000][Jones et al., 2000]]
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
If we're not going to provide a multi-backend solution, I suggest to
keep things simple and write LaTeX code directly (or use the solution
provided by Eric). Unless you have something else in mind with these
link abbrevs, of course.
Hi Bastien,
Bastien b...@altern.org writes:
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
If we're not going to provide a multi-backend solution, I suggest to
keep things simple and write LaTeX code directly (or use the solution
provided by Eric). Unless you have something else
2013ko martxoak 6an, Bastien-ek idatzi zuen:
I'd suggest to treat org-link-abbrev-alist and locally defined
abbreviated links differently when opening the link at point and
when exporting the buffer.
At expand time, the exporter could attach a list of export functions
(filters?) to the
I have the following defined in my org customisation:
#+begin_src org
(org-add-link-type cite 'ebib
(lambda (path desc format)
(cond
((eq format 'latex)
(format \\cite{%s} path)
#+end_src
which allows me to
On Mon, Mar 04, 2013 at 10:10:37AM +0530, Vikas Rawal wrote:
I have a website that is built using old exporter. It used
org-exp-bibtex. I will move it to the new exporter, and if there is a
problem, get back to the mailing list.
I think people should be using maint instead of master for
Le dimanche 3 mars 2013 à 08h06, Vikas Rawal a écrit:
org-exp-bibtex seems to have gone missing from git repository. Can
somebody confirm pleae.
Vikas
Dear Vikas,
I do confirm.
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to
Hi Vikas,
François Allisson franc...@allisson.co writes:
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to contrib/oldexp during the process of
migration towards org new exporter. And yesterday, the directory
contrib/oldexp was eventually
Bastien b...@altern.org writes:
Hi Vikas,
François Allisson franc...@allisson.co writes:
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to contrib/oldexp during the process of
migration towards org new exporter. And yesterday, the directory
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@altern.org writes:
Hi Vikas,
François Allisson franc...@allisson.co writes:
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to contrib/oldexp during the process of
migration towards
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@altern.org writes:
Hi Vikas,
François Allisson franc...@allisson.co writes:
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from
I do confirm.
Thank you. I have been trying to migrate to the new-exporter. I have
not had much success so far but I hope to be able to figure it all out
soon. Since we do not yet have a documentation, it is difficult.
Nicolas has been very kind with help.
I have a website that is built
org-exp-bibtex seems to have gone missing from git repository. Can
somebody confirm pleae.
Vikas
44 matches
Mail list logo
