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

From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Something to watch out for when including files
Date: Wed, 21 Sep 2016 07:44:50 +0100	[thread overview]
Message-ID: <874m594uql.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <58a8c0419a56444fb6956cd709d26dec@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Charles C. Berry's message of "Tue, 20 Sep 2016 23:32:05 +0000")

On Tuesday, 20 Sep 2016 at 23:32, Charles C. Berry wrote:
> I find myself in the habit of using inlinetasks tagged noexport for 
> various things and that might serve you in this case. That is, convert the 
> headline section to an inlinetask.

Hi Chuck,

Yes, this would work.  But, in the end, simply removing the section was
sufficient as it really wasn't necessary (and that's why I have
everything under version control... ;-).

> Another possibility is to use something like:
>
> #+header: :exports results :results raw replace
> #+NAME: import-include-dot-org
>
> #+BEGIN_SRC emacs-lisp
>    (require 'ox-org)
>    (org-export-string-as "#+INCLUDE: include.org" 'org t)
> #+END_SRC
>
> which will strip out headlines tagged with noexport during the babel phase 
> of export (i.e. before parsing).

This is quite ingenious!  I like it.  Don't need it now but worth
keeping note of for the future.  Thanks.

>> I do wonder whether the org export approach (i.e. how it "includes"
>> files) is correct but I can understand why the implementation is the way
>> it is.
>
> I agree about the implementation. Trying to make it smarter is asking for 
> trouble.

Yes, probably.

Thanks again,
eric


-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.90.1, Org release_8.3.3-535-g7213aa

next prev parent reply	other threads:[~2016-09-21  7:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 15:21 Something to watch out for when including files Eric S Fraga
2016-09-20 17:10 ` Adam Porter
2016-09-20 23:32 ` Charles C. Berry
     [not found] ` <58a8c0419a56444fb6956cd709d26dec@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-21  6:44   ` Eric S Fraga [this message]
2016-09-21 15:22 ` Giacomo M
     [not found] ` <b81ae1e313fc4a0c85fa5d63e3c29eb2@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-21 15:53   ` Eric S Fraga

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=874m594uql.fsf@delle7240.chemeng.ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=ccberry@ucsd.edu \
    --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

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