From: Subhan Michael Tindall <SubhanT@familycareinc.org>
To: "Daniel J. Sinder" <djsinder@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Sub-tree EXPORT_ properties are not over-riding file-level options
Date: Thu, 13 Nov 2014 21:28:15 +0000 [thread overview]
Message-ID: <022f7cd1f7474f389c9b080c0b5867c4@fbmailsvr1.familycareinc.org> (raw)
In-Reply-To: <CALEVMAUsxBvHXeq4pq6P4GFogiTHuLtS=MV07D5H-Q9HYqLY+A@mail.gmail.com>
>From: emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org [mailto:emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org] On >Behalf Of Daniel J. Sinder
>Sent: Thursday, November 13, 2014 12:29 PM
>To: emacs-orgmode
>Subject: Re: [O] Sub-tree EXPORT_ properties are not over-riding file-level options
>
>On Thu, Nov 13, 2014 at 10:14 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
>The EXPORT_ properties are only meaningful when you do a subtree export,
>i.e., Export scope is "Subtree" in export dispatcher.
>
>Thank you! That does the trick.
>
>I must say, this is a little confusing because an active region limits the output of the export to the active region. Thus, the output of a single subtree >misled me to believe that the "scope" of the export had been already limited to "Subtree."
>
>I now see the variable org-export-initial-scope, but that's a little too heavy handed (since one can't export the entire file if it is left set to Subtree. It >would be nice if there was some way to have 'C-c @' automatically (and temporarily) set this variable to Subtree until the next export or until the >region is de-activated.
>
>Thanks again,
>Dan
C-c C-e followed by C-s limits the export scope to the subtree at point quite nicely in my experience. It resets when the dispatcher is closed
This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
prev parent reply other threads:[~2014-11-13 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 3:58 Sub-tree EXPORT_ properties are not over-riding file-level options Daniel J. Sinder
2014-11-13 18:14 ` Nicolas Goaziou
2014-11-13 20:29 ` Daniel J. Sinder
2014-11-13 21:28 ` Subhan Michael Tindall [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=022f7cd1f7474f389c9b080c0b5867c4@fbmailsvr1.familycareinc.org \
--to=subhant@familycareinc.org \
--cc=djsinder@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).