From: Daniel P Gomez <gomez.danp@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Weird interaction between ox-extra and include :minlevel
Date: Thu, 12 Apr 2018 16:38:03 +0200 [thread overview]
Message-ID: <CAJTMgxgFWN1E=EL2dy4K4fZSvk-iMM9tJ9WKKv7UycHx-8_mrQ@mail.gmail.com> (raw)
In-Reply-To: <87in8wy2nm.fsf@nicolasgoaziou.fr>
I was thinking of #+ignore_tags. as an analog of #+exclude_tags. While
#+exclude_tags removes a complete subtree from export, #+ignore_tags
would only ignore headlines and insert the contents.
When used in combination, subtree would be excluded no matter what.
#+IGNORE_TAGS: ignore bar
#+EXLUDE_TAGS: noexport foo
The idea of ignore_tags, for me, would to allow grouping content
within the Org file in a manner that differs from the grouping of
content upon export - without having to resort to filter-hooks. Not
that hooks are bad, but they are harder to construct without proper
elisp skills and require knowledge about the Org API. Furthermore,
tags are excellent because they're easy to manipulate and search for.
On Thu, Apr 12, 2018 at 3:28 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> "Daniel P. Gomez" <gomez.danp@gmail.com> writes:
>
>> Is there any intention of bringing ox-extra functionality into main
>> Org? Something like #+ignore_tags would be a powerful addition for
>> fine grained export control, in my opinion.
>
> IIRC, "ox-extra" was written because we could not agree on a definition
> and an implementation of the ignore headline feature.
>
> I don't know what you do mean by "something like #+ignore_tags", but you
> could discuss it on this ML.
>
> Regards,
>
> --
> Nicolas Goaziou
next prev parent reply other threads:[~2018-04-12 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 9:26 Bug: Weird interaction between ox-extra and include :minlevel Daniel P. Gomez
2018-04-12 13:28 ` Nicolas Goaziou
2018-04-12 14:38 ` Daniel P Gomez [this message]
2018-04-15 7:44 ` Nicolas Goaziou
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='CAJTMgxgFWN1E=EL2dy4K4fZSvk-iMM9tJ9WKKv7UycHx-8_mrQ@mail.gmail.com' \
--to=gomez.danp@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).