emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Feature Request: Specifying a 'master file' in included files [9.0.1 (9.0.1-elpa @ /home/schnecki/.emacs.d/elpa/org-20161118/)]
Date: Wed, 14 Dec 2016 10:27:47 +0100	[thread overview]
Message-ID: <87fulqzwq4.fsf@gmx.us> (raw)
In-Reply-To: 874m29w86v.fsf@uibk.ac.at

Hi Manuel,

Manuel Schneckenreither <manuel.schneckenreither@uibk.ac.at> writes:

> I have a feature request. It would be awesome if there was a master file setup
> similar to auctex such that whenever an export is started while residing in an
> included file the export is automatically called from the master buffer (main file
> with headers and all includes). This would generate the desired exported document
> (html,LaTeX,...). Currently, something similar may be done using the publishing,
> but this only works for HTML exports. I'm thinking of something like following at
> the top of the included file:

Why does it only work for html export?  You can chose whichever export
backend you want for publishing projects.  There’s even a "current
project" option in C-c C-e.  Of course you’d need to explicitly add the
projects you need.

> # Set master in file introduction.org
> #+MASTER_FILE: main.org  # possibly even with relative path, like ../main.org

I have no opinion on whether it’s worth having such a keyword.

Thanks,
Rasmus

-- 
This space is left intentionally blank

  reply	other threads:[~2016-12-14  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 14:09 Bug: Feature Request: Specifying a 'master file' in included files [9.0.1 (9.0.1-elpa @ /home/schnecki/.emacs.d/elpa/org-20161118/)] Manuel Schneckenreither
2016-12-14  9:27 ` Rasmus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-12 14:10 Manuel Schneckenreither

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=87fulqzwq4.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).