emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Daniel P Gomez <gomez.danp@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Weird interaction between ox-extra and include :minlevel
Date: Sun, 15 Apr 2018 09:44:48 +0200	[thread overview]
Message-ID: <87k1t8lxqn.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJTMgxgFWN1E=EL2dy4K4fZSvk-iMM9tJ9WKKv7UycHx-8_mrQ@mail.gmail.com> (Daniel P. Gomez's message of "Thu, 12 Apr 2018 16:38:03 +0200")

Hello,

Daniel P Gomez <gomez.danp@gmail.com> writes:

> 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.

You may want to read the discussions about this feature on the ML.

I think "only" is not accurate. To make it clear, what would become the
following documents:

--8<---------------cut here---------------start------------->8---
* H

Text

** H2 :ignore:

Text 2

*** H3
--8<---------------cut here---------------end--------------->8---

and

--8<---------------cut here---------------start------------->8---
Text 0

* H :ignore:

Text

** H2

Text 2
--8<---------------cut here---------------end--------------->8---

but also

--8<---------------cut here---------------start------------->8---
- item
* H :ignore:
- new list?
--8<---------------cut here---------------end--------------->8---

and the following convoluted one

--8<---------------cut here---------------start------------->8---
#+begin_example

Something

* H :ignore:

Somethin else
#+end_example
--8<---------------cut here---------------end--------------->8---

> When used in combination, subtree would be excluded no matter what.
>
> #+IGNORE_TAGS: ignore bar
> #+EXLUDE_TAGS: noexport foo

I'm not sure to understand this.

> 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.

The manual gives one example of one such hook, see (info "(org) Advanced
configuration"). There, the filter /only/ removes headlines.

Regards,

-- 
Nicolas Goaziou

     prev parent reply	other threads:[~2018-04-15  7:44 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
2018-04-15  7:44     ` Nicolas Goaziou [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=87k1t8lxqn.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=gomez.danp@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

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).