From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: Org mailing list <emacs-orgmode@gnu.org>
Subject: Re: Announcement: org-one-to-many
Date: Thu, 12 Feb 2015 15:43:08 -0800 [thread overview]
Message-ID: <m2lhk2n1bn.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <87386a3gl4.fsf@wmi.amu.edu.pl>
I think it would be easy to copy all the file keywords. One way would
just be searching by regexp. Another way could be similar to:
http://kitchingroup.cheme.cmu.edu/blog/2013/05/05/Getting-keyword-options-in-org-files/
if you know in advance what the important ones are.
Marcin Borkowski writes:
> Hello everybody,
>
> so I've got this little library of mine, called org-one-to-many, which
> can split an Org file into pieces, modifying internal links so that they
> still point to the same place (even if now in another file).
>
> But I have a problem with it. I would like to export all the resulting
> files into, say, HTML, and the problem is that all the options
> (obviously) don't propagate to the “subfiles” – so that if I say e.g.
>
> #+LANGUAGE: pl
>
> anywhere in the file, it is not copied to all the resulting files
> (generated from headings), unless this line happens to be in one of them
> (and then it disappears from the “main” file).
>
> I can see two solutions to this problem. One is to somehow recognize
> these lines and copy them to all the resulting files. One trouble with
> that is that I’d have to decide, for instance, /where/ to put them – at
> the beginning?
>
> The easier solution, which /might/ also be “cleaner” in a sense, is to
> recognize some kind of “special” heading - for instance,
>
> * COMMENT Config
> #+LANGUAGE: pl
>
> or something like that, and copy it verbatim to all the generated files,
> say – at their end.
>
> What do you think? Can you see another solution? If not, which of the
> above do you consider a better one?
>
> TIA,
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-02-12 23:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 15:02 Announcement: org-one-to-many Marcin Borkowski
2014-10-21 16:10 ` Eric Abrahamsen
2014-10-21 16:58 ` Marcin Borkowski
2014-10-23 14:39 ` Daniel Clemente
2014-10-23 17:58 ` Marcin Borkowski
2014-10-24 4:06 ` Daniel Clemente
2015-02-12 22:33 ` Marcin Borkowski
2015-02-12 23:43 ` John Kitchin [this message]
2015-02-13 0:13 ` Marcin Borkowski
2015-02-13 0:34 ` John Kitchin
2015-02-13 8:44 ` Sebastien Vauban
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=m2lhk2n1bn.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).