emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: lunaryorn@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Limit subtree to a specific export backend
Date: Fri, 04 Oct 2013 14:36:20 +0200	[thread overview]
Message-ID: <87wqltp60r.fsf@gmx.us> (raw)
In-Reply-To: <CALf2awT=1WJqouKRoyrchiEfu88AUAh24qhM=uqvr4V=YPke=Q@mail.gmail.com> (Sebastian Wiesner's message of "Fri, 4 Oct 2013 12:33:16 +0200")

Sebastian Wiesner <lunaryorn@gmail.com> writes:

> I presume, I can set "org-export-filter-options-functions" as a
> directory-local variable, so that this kind of export restrictions
> only applies to Org mode documents in the specific project.

Probably.  There was some discussions on it lately.  Check the
archive.

>> Here's an example that's perhaps a bit too verbose and not thoroughly
>> tested:
>>
>> #+BEGIN_SRC Org
>> #+TITLE: Conditional export
>> #+options: tags:nil
>> * Common intro
>>   txt
>> ** Pdf heading                                                        :latex:
>>    the math is really pretty!
>> ** HTML heading                                                        :html:
>>    the text features hyperlinks!
>> ** More common notes
>>    Intro over
>>
>> * Code                                                             :noexport:
>> #+begin_src emacs-lisp
>>   (defun rasmus/conditional-export (settings backend)
>>     "Change SETTINGS to include dynamically set export-tags.
>>
>>     Enable the use of BACKEND as EXPORT_TAGS.  A derived backend is
>>     treated as its parent."
>>     (let ((backends (remove-duplicates
>>                      (mapcar (lambda (x)
>>                                (or (org-export-backend-parent x)
>>                                    (org-export-backend-name x)))
>>                              org-export--registered-backends)))
>>           ;; for treating derived backend and parent backends differently:
>>           ;; (backend-or-parent backend)
>>           (backend-or-parent (dolist (b org-export--registered-backends return)
>>                                (when  (eq (org-export-backend-name b) backend)
>>                                  (return (or (org-export-backend-parent b)
>>                                              (org-export-backend-name b)))))))
>>       (plist-put
>>        settings :exclude-tags
>>        (append (plist-get settings :exclude-tags)
>>                (mapcar 'symbol-name
>>                        (remove backend-or-parent backends))))))
>>
>>   (add-to-list 'org-export-filter-options-functions 'rasmus/conditional-export)
>> #+end_src
>> #+END_SRC
>
> Do I understand correctly, that this code adds all *other* backends to
> the "exclude-tags" setting, instead of adding the current one to
> "select-tags"?  Is there a specific reason to do this?

Let me know if it doesn't work as desired and share your improvements.
I didn't do proper testing as I don't fully appreciate all corner
cases of the use case.


On select tag, you can use it if you like how this document works 

#+SELECT_TAGS: latex
* common intro
  test 
** html intro                                                          :html:
   html
** latex                                                              :latex:
   latex
* common next section 
  Next section

> Just adding "backend" to "select-tags" seems simpler to me, and I
> wonder whether "exclude-tags" even behaves correctly for headlines
> with more than one tag.  As far as I understand the Org manual, it
> would exclude headlines tagged as ":html:latex:" when exporting to
> "html", because "latex" is added as exclude-tag, preventing the
> headline from being exported.

You should be able to test this in a normal org document.

–Rasmus

-- 
C is for Cookie

      reply	other threads:[~2013-10-04 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 14:06 Limit subtree to a specific export backend Sebastian Wiesner
2013-09-30 14:24 ` Sebastien Vauban
2013-10-03 22:27   ` Sebastian Wiesner
2013-10-04  7:21     ` Sebastien Vauban
2013-09-30 16:03 ` Rasmus
2013-10-04 10:33   ` Sebastian Wiesner
2013-10-04 12:36     ` 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=87wqltp60r.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    --cc=lunaryorn@gmail.com \
    /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).