Uwe Brauer writes:
>>> "Nick" == Nick Dokos writes:
>
>> Uwe Brauer writes:
> "Eric" == Eric S Fraga writes:
>>>
>>> > Uwe Brauer writes:
>
>> (require 'ox)
>
>> is the closest equivalent. But the exporter has changed so much that it
>> would not be surprisi
Uwe Brauer writes:
>> (require 'ox)
>> is the closest equivalent. But the exporter has changed so much that it
>> would not be surprising if this doesn't work either.
> It does not work, but as I found out I have much more fundamental
> problems with the new org-8 version than I thought[1]
org-p
>> "Nick" == Nick Dokos writes:
> Uwe Brauer writes:
"Eric" == Eric S Fraga writes:
>>
>> > Uwe Brauer writes:
> (require 'ox)
> is the closest equivalent. But the exporter has changed so much that it
> would not be surprising if this doesn't work either.
It doe
>> "Achim" == Achim Gratz writes:
> Uwe Brauer writes:
>> >> - 7.8.X had a file called org-exp.el. This file is now gone. What is
>> >> it substitute???
>>
>> > What functionality is it you need from that file?
>>
>> I checked: this is the *essential* file to use
>> or
Uwe Brauer writes:
>>> - 7.8.X had a file called org-exp.el. This file is now gone. What is
>>> it substitute???
>
>> What functionality is it you need from that file?
>
> I checked: this is the *essential* file to use
> org-preview-latex-fragment in a
> matlab-mode buffer or in a gn
Uwe Brauer writes:
>>> "Eric" == Eric S Fraga writes:
>
>> Uwe Brauer writes:
>>> Hello
>>>
>>> Thanks to Achim's change in org-compat, I could compile and load the new
>>> orgmode, without the complain about the obsolete function stuff.
>>>
>>> However there are s
>> "Eric" == Eric S Fraga writes:
> Uwe Brauer writes:
>> Hello
>>
>> Thanks to Achim's change in org-compat, I could compile and load the new
>> orgmode, without the complain about the obsolete function stuff.
>>
>> However there are still serious problems:
>>
>> -
Hi Aaron,
Aaron Ecay 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 this after Org 8.0,
a
Hi Li,
Li Bowen writes:
> With the org-mode 8 new exporter, org-exp-bibtex.el doesn't work any
> longer. I tried to change export hook to
> org-export-before-preprocess-hook, but it is more complicated than I
> hoped. I am looking for a patch, not urgent. Many thanks.
Yes, this is a known issue
With the org-mode 8 new exporter, org-exp-bibtex.el doesn't work any
longer. I tried to change export hook to
org-export-before-preprocess-hook, but it is more complicated than I
hoped. I am looking for a patch, not urgent. Many thanks.
Below is my test file.
##
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 t
Jambunathan K writes:
> Andreas Leha 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-not
Jambunathan K 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 changes in Footnot
Jambunathan K 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 sometime (when it wil
Nicolas Goaziou 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 as it
comes to my
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?
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 off
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. B
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
> Org-Bibtex
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::key&&prenote=my prenote&&postnote=my postnote]]
>
> [[http://perdu.com&&title=You're lost?]]
>
> Thi
Aloha Rasmus,
Rasmus 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.
>
> There ar
t...@tsdye.com (Thomas S. Dye) writes:
> Rasmus writes:
>
>> Achim Gratz writes:
>>
Do you mean using something like this
[[file:my.bib&key=key;prenote=note1;postnote=note2][key]]
for the file: protocol
>>>
>>> This is a prime example of how _not_ to do this, IMHO. T
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.orgmode as well.
Achim Gratz writes:
>> Do you mean using something like this
>>
>> [[file:my.bib&key=key;prenote=note1;postnote=note2][key]]
>>
>> for the file: protocol
>
> This is a prime example of h
Rasmus writes:
> Achim Gratz writes:
>
>>> Do you mean using something like this
>>>
>>> [[file:my.bib&key=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
Achim Gratz writes:
>> Do you mean using something like this
>>
>> [[file:my.bib&key=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 extra
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
Hi Achim,
Achim Gratz 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 called
> URN/U
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 h
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 al
Bastien 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-li
Hi Bastien,
On Thu, Mar 7, 2013 at 6:16 AM, Bastien 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:
> [[type:key;pre;p
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 pr
Hi Bastien,
On Thu, Mar 7, 2013 at 5:21 AM, Bastien 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-l
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
Andreas Leha 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 and
post-note attached to it.
I
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 simple cite: (and
Hi Bastien,
Bastien writes:
> Hi Andreas,
>
> Andreas Leha 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]]
Hi Andreas,
Andreas Leha 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 file.
The config happens in the #
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
Hi Bastien,
Bastien writes:
> Hi Nicolas,
>
> Nicolas Goaziou 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
>> lin
Hi Nicolas,
Nicolas Goaziou 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.
Can you resend me
Nicolas Goaziou writes:
> Hello,
>
> Bastien writes:
>
>> Hi Andreas and all,
>>
>> Andreas Leha writes:
>>
>>> Eric suggested/uses this format (thanks for sharing, Eric):
>>> [[cite:jones-etal-2000][Jones et al., 2000]]
>>> ^^^ ^^
>>> key
Hello,
Bastien writes:
> Hi Andreas and all,
>
> Andreas Leha 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
Hi Andreas and all,
Andreas Leha 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 treat org-link-abbrev-alist and loc
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> Nicolas Goaziou writes:
>>
>>> Bastien writes:
>>>
Hi Vikas,
François Allisson writes:
> org-exp-bibtex, because of its dependency on the old exporter, was first
> moved from contrib/lisp to contrib/old
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 p
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
>
> 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 usi
Hello,
Andreas Leha writes:
> Nicolas Goaziou writes:
>
>> Bastien writes:
>>
>>> Hi Vikas,
>>>
>>> François Allisson 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 t
Nicolas Goaziou writes:
> Bastien writes:
>
>> Hi Vikas,
>>
>> François Allisson 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
Bastien writes:
> Hi Vikas,
>
> François Allisson 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 eve
Hi Vikas,
François Allisson 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 removed[1].
Yes. W
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 contrib/ol
org-exp-bibtex seems to have gone missing from git repository. Can
somebody confirm pleae.
Vikas
This patch has now been accepted.
- Carsten
On Sep 12, 2011, at 10:26 PM, Nik Putnam wrote:
> Dear Taru and orgmode community,
>
> Org-mode export to HTML is a really useful thing, and I love the
> bibtex integration.
>
> I had a problem exporting from org-mode to HTML, with bibtex. I was
> a
Dear Taru and orgmode community,
Org-mode export to HTML is a really useful thing, and I love the
bibtex integration.
I had a problem exporting from org-mode to HTML, with bibtex. I was
able to fix it with a change to a regular expression
org-exp-bibtex.el. The diff is shown below.
(My bibtex
56 matches
Mail list logo
