Rasmus ras...@gmx.us writes:
hmmm... the sometimes makes me nervous. I found even for links, this
only works sometimes. That doesn't seem reliable to me.
I think extending existing backends
(e.g. http://orgmode.org/manual/Advanced-configuration.html) is probably
more reliable for getting element
Hi John,
John Kitchin jkitc...@andrew.cmu.edu writes:
hmmm... the sometimes makes me nervous. I found even for links, this
only works sometimes. That doesn't seem reliable to me.
With headlines the case where it does not work is for verb-only
headings. I guess that could occur more
Daimrod daim...@gmail.com writes:
Why don't you just define how the link should be exported in your link
definition?
for example:
https://github.com/jkitchin/jmax/blob/master/org/org-ref.org#the-links
You can see a link that is defined, with different export formats for
different backends.
I
John Kitchin jkitc...@andrew.cmu.edu writes:
I too am wondering if there is a defined way to get to the element
properties within a filter function.
qNo. But sometimes you can recover it from the text-properties, if it
is not a verb, (~·~, =·=). Her's an example:
(defun
Hi,
I've wrote a simple filter to customize how links are exported in
latex:
#+BEGIN_SRC
(defun dmd--latex-bib-link-filter (data backend info)
Convert a bib link to a citation (e.g. bib:foo93 - \cite{foo93}).
(let* ((beg (next-property-change 0 data))
(link (if beg (get-text-property
