From: Ihor Radchenko <yantar92@posteo.net>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: the opposite of the noexport tag
Date: Sun, 22 Oct 2023 17:22:29 +0000 [thread overview]
Message-ID: <87edhma7xm.fsf@localhost> (raw)
In-Reply-To: <87pm16oahw.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
> I tried
> ,----
> |
> | #+options: SELECT_TAGS: noexport
> | #+options: EXCLUDE_TAGS: export
This is not a correct format. Please, review the manual section I linked
to.
(side note: this is odd to set selected tags to "noexport")
#+SELECT_TAGS: noexport
#+EXCLUDE_TAGS: export
* First section
* Second :export:
This
* third
That
> ...
> That almost worked when exporting to LaTeX, the resulting file looks
> like
>
>
> ,----
> | \section{Second\hfill{}\textsc{export}}
> | \label{sec:orgfba34a2}
> | This
> `----
>
> I presumed the tag :export does not get exported, but it does, any
> chance to avoid that, as well?
Please use the correct formatting.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-22 17:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 15:23 the opposite of the noexport tag Uwe Brauer
2023-10-22 16:18 ` Bruno Barbier
2023-10-22 16:33 ` Uwe Brauer
2023-10-22 16:42 ` Ihor Radchenko
2023-10-22 17:03 ` Uwe Brauer
2023-10-22 17:22 ` Ihor Radchenko [this message]
2023-10-22 19:38 ` Uwe Brauer
2023-10-23 8:19 ` Ihor Radchenko
2023-10-23 12:16 ` Uwe Brauer
2023-10-23 12:32 ` Ihor Radchenko
2023-10-23 12:34 ` Uwe Brauer
2023-10-23 12:59 ` Uwe Brauer
2023-10-23 13:23 ` Loris Bennett
2023-10-24 9:01 ` Ihor Radchenko
2023-10-24 9:40 ` Loris Bennett
2023-10-24 11:06 ` Ihor Radchenko
2023-10-25 8:27 ` Ihor Radchenko
2023-10-24 12:22 ` Uwe Brauer
2023-10-22 16:58 ` Bruno Barbier
2023-10-22 17:06 ` Uwe Brauer
2023-10-22 17:19 ` Bruno Barbier
2023-10-22 19:35 ` Uwe Brauer
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=87edhma7xm.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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).