From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: export select tag behavior and documentation
Date: Sat, 31 Oct 2020 21:16:54 -0700 [thread overview]
Message-ID: <CAJcAo8uLrAQ5qo8DgkagHYcQUfKat=YkC1qVUjCy3J6U5yREDg@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8uZsr_bJ1kDSQsyxSOxK7uVqCKfqZ=uQ+LXQ6Ev4gvHfA@mail.gmail.com>
huh, in exporting the email, i found a possible export bug.
here is the original. please reply to this one.
notice that a whole paragraph got deleted in the previous email. that
is the exported version. dunno why.
9.4 maint docstring
===
org-export-select-tags is a variable defined in ‘ox.el’.
...
If any such tag is found in a buffer, all trees that do not carry
one of these tags will be ignored during export.
===
1) does this take into account subtree export, region
export, and narrowed buffers? if so, perhaps the
docstring should change.
my expectation is that just having :export: in a huge
buffer should not affect exporting a tiny part of it.
by the principle of least surprise.
it is sorta surprising enough that something buried in a
subtree can affect the whole export of that subtree. :)
2) org-export-with-tasks set to
- nil will not export a task subtree regardless of :export: tag underneath
- t will export regardless
thus basically overriding the export tag feature with the
export with tasks feature. is that intended? i can see
that it could be the best choice, but could also see it
being useful to use the export tag even with tasks.
i wonder when was the last time there was a change to
this variable or its behavior? i suspect there might
have been a change, at least wrt top level todo kw
stopping export, but i don't know.
On 10/31/20, Samuel Wales <samologist@gmail.com> wrote:
> [2020-10-31 Sat 20:59] =x
>
> bug
> ===
>
> 9.4 maint docstring
>
> === org-export-select-tags is a variable defined in
> ‘ox.el’.
>
> ...
>
>
> 1) does this take into account subtree export, region
> export, and narrowed buffers? if so, perhaps the
> docstring should change.
>
> my expectation is that just having :export: in a huge
> buffer should not affect exporting a tiny part of it.
> by the principle of least surprise.
>
> it is sorta surprising enough that something buried
> in a subtree can affect the whole export of that
> subtree. :)
>
> 2) org-export-with-tasks set to
>
> - nil will not export a task subtree regardless of
> :export: tag underneath
> - t will export regardless
>
> thus basically overriding the export tag feature with
> the export with tasks feature. is that intended? i
> can see that it could be the best choice, but could
> also see it being useful to use the export tag even
> with tasks.
>
> i wonder when was the last time there was a change to
> this variable or its behavior? i suspect there might
> have been a change, at least wrt top level todo kw
> stopping export, but i don't know.
>
--
The Kafka Pandemic
Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
prev parent reply other threads:[~2020-11-01 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 3:59 export select tag behavior and documentation Samuel Wales
2020-11-01 4:16 ` Samuel Wales [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='CAJcAo8uLrAQ5qo8DgkagHYcQUfKat=YkC1qVUjCy3J6U5yREDg@mail.gmail.com' \
--to=samologist@gmail.com \
--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).