emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Help on org-export-filter-link-functions
Date: Mon, 06 Oct 2014 00:24:48 +0200	[thread overview]
Message-ID: <87vbnym9xr.fsf@gmx.us> (raw)
In-Reply-To: m2mw9a64r3.fsf@andrew.cmu.edu

Hi John,

John Kitchin <jkitchin@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 frequently with links, though
I have never done anything serious with links. q  

> I think extending existing backends
> (e.g. http://orgmode.org/manual/Advanced-configuration.html) is probably
> more reliable for getting element properties, and approximately the same
> amount of work.
 
In practice derived classes could be a lot of work.

There is also two hooks that run before processing, but you'd need to
be able to solve the issue with org syntax.  In practice this is not a
limitation as you can use snippets for whatever backend.

> I guess it just depends on how significantly you are modifying the
> export, and what information you need to modify it. Filters are great
> for simple wrapping and regexp based modifications. A derived backend is
> better if you need reliable element properties, and a different format
> than the default export.

Yeah.

–Rasmus

-- 
I almost cut my hair, it happened just the other day

      reply	other threads:[~2014-10-05 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 11:19 Help on org-export-filter-link-functions Daimrod
2014-10-04 16:40 ` John Kitchin
2014-10-05  1:13   ` Rasmus
2014-10-05 13:11     ` John Kitchin
2014-10-05 22:24       ` Rasmus [this message]

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=87vbnym9xr.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    /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).