From: Vicente Vera <vicentemvp@gmail.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: "Minimal" LaTeX export
Date: Sat, 16 Dec 2017 21:45:59 +0000 [thread overview]
Message-ID: <CAMfbzvAW7irkpddzuYKgg1PmQV6x_Sqdi25B7vB2XkwzBK=2ng@mail.gmail.com> (raw)
In-Reply-To: <15A14D4F-5BBB-4B45-AB4F-A32E171CE0DA@ucsd.edu>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
That is amazing. Thank you very much!
Yes, that's a good idea (include files); will look into it.
El dic 16, 2017 2:46 PM, "Berry, Charles" <ccberry@ucsd.edu> escribió:
> On Dec 16, 2017, at 8:48 AM, Vicente Vera <vicentemvp@gmail.com> wrote:
>
> I'm trying to export a simple document to a LaTeX buffer, but just the
> main content, without a preamble nor the "document" environment.
You want `(org-latex-export-as-latex nil nil nil t)' or `C-c C-e C-b l L'.
,----[ C-h f org-latex-export-as-latex RET ]
| org-latex-export-as-latex is an interactive autoloaded compiled Lisp
| function in ‘ox-latex.el’.
|
| (org-latex-export-as-latex &optional ASYNC SUBTREEP VISIBLE-ONLY
| BODY-ONLY EXT-PLIST)
|
| Export current buffer as a LaTeX buffer.
|
| [...]
|
| When optional argument BODY-ONLY is non-nil, only write code
| between "\begin{document}" and "\end{document}".
|
| [...]
`----
> The main objective is to export several Org documents which are parts of a
> larger LaTeX report. These parts are then included by means of the
> "input" command.
Why not use include keywords in the org document? They can, if needed,
refer to sections in the parent document.
See (info "(org) Include files")
HTH,
Chuck
[-- Attachment #2: Type: text/html, Size: 1954 bytes --]
prev parent reply other threads:[~2017-12-16 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 16:48 "Minimal" LaTeX export Vicente Vera
2017-12-16 17:33 ` Rasmus
2017-12-16 17:46 ` Berry, Charles
2017-12-16 21:45 ` Vicente Vera [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='CAMfbzvAW7irkpddzuYKgg1PmQV6x_Sqdi25B7vB2XkwzBK=2ng@mail.gmail.com' \
--to=vicentemvp@gmail.com \
--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
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).