From: David Bremner <david@tethera.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: custom function for org-babel src block export
Date: Mon, 25 Dec 2023 18:26:45 -0800 [thread overview]
Message-ID: <87jzp1hf6i.fsf@tethera.net> (raw)
In-Reply-To: <877cl2lzcz.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> David Bremner <david@tethera.net> writes:
>
>> I am generating slides using org-beamer. I would like certain code
>> blocks to export as links containing URL-encoded content of the
>> block.
>
> Check out https://orgmode.org/manual/Advanced-Export-Configuration.html
> You may use export filter or extend ox-beamer backend, creating a new
> custom backend that will export your code blocks as desired.
>
Thanks for the suggestion(s).
I tried defining org-export-filter-src-block-functions (see end)
but I encountered two issues
1) The text already includes the latex environment (in my case
listings). This is solvable, but did make me wonder if I was using the
right filter.
2) I could not figure out how to cleanly access the source language
(e.g. "stacker" in my example). It didn't seem to be in "info". I
guess I can recover it from the text using e.g. regex, but this seems fragile, since
it would break when switching backends.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(defun db-ox-src-filter (text backend info)
(when (org-export-derived-backend-p backend 'latex)
(db-stacker-link text)))
(add-to-list 'org-export-filter-src-block-functions
#'db-ox-src-filter)
next prev parent reply other threads:[~2023-12-26 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 21:49 custom function for org-babel src block export David Bremner
2023-12-25 21:57 ` Ihor Radchenko
2023-12-26 2:26 ` David Bremner [this message]
2023-12-26 6:31 ` David Bremner
2023-12-26 13:12 ` Rudolf Adamkovič
2023-12-26 14:36 ` David Bremner
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=87jzp1hf6i.fsf@tethera.net \
--to=david@tethera.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).