From: Uwe Brauer <oub@mat.ucm.es>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-orgmode@gnu.org
Subject: Re: the opposite of the noexport tag
Date: Tue, 24 Oct 2023 14:22:05 +0200 [thread overview]
Message-ID: <87fs20p5w2.fsf@mat.ucm.es> (raw)
In-Reply-To: 871qdk8kd9.fsf@localhost
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
> I find this part confusing - we first talk about no "export" tags at all
> and then immediately about using with "export" tags. I dropped it in the
> attached patch. Maybe there is a better way to formulate the same?
> In the attached patch, I incorporated your other changes, the grammar
> remarks from Loris, and reworded a bit more.
That looks good to me thanks. I appreciate the sentence
,----
| + Note that a file without the =export= or the =noexport= tag will
| + export all its sections.
`----
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2023-10-24 12:22 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
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 [this message]
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=87fs20p5w2.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).