On Jan 12, 2009, at 5:09 PM, Friedrich Delgado Friedrichs wrote:
Hiho
Carsten Dominik schrieb:
On Jan 9, 2009, at 5:59 PM, Friedrich Delgado Friedrichs wrote:
same relative path ./ - work
or the other way round it's . - ../
This is exactly what I meant, and how it works in my own test case
Hiho
Carsten Dominik schrieb:
On Jan 9, 2009, at 5:59 PM, Friedrich Delgado Friedrichs wrote:
same relative path ./ - work
or the other way round it's . - ../
This is exactly what I meant, and how it works in my own test case
here
--Zitatende---
Ok, works here too. The id locations
Hi Friedrich,
first of all, Org does expect that the file containing
the link and the file containing the target have the same
relative path both in the staging area (where the .org files are)
and in the publishing area (where the .html files will be). I don't
know how else to approach this.
Hiho!
Carsten Dominik schrieb:
first of all, Org does expect that the file containing
the link and the file containing the target have the same
relative path both in the staging area (where the .org files are)
and in the publishing area (where the .html files will be). I don't
know how else
On Jan 9, 2009, at 5:59 PM, Friedrich Delgado Friedrichs wrote:
Hiho!
Carsten Dominik schrieb:
first of all, Org does expect that the file containing
the link and the file containing the target have the same
relative path both in the staging area (where the .org files are)
and in the
Hi!
I really like org-link-to-org-use-id, however it breaks links to
org items in html export for me.
I have the following test file:
** Test [[id:45c4a467-b6ee-497c-9ed7-40342738e1c2][Item in a different
org-file]]
- [[id:frz5htg0rhe0][Yet another item in a different org file]]
Hi Friedrich,
thanks for bringing this up. Yes, this should work.
Back when I did the id links, I thought it would be very hard,
but fortunately I did put the basic framework for additional
targets in place already a while ago, in response to a request
by Matt for hard targets that are good for
