From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ox, patch] external compilation
Date: Fri, 20 Feb 2015 19:21:43 +0100 [thread overview]
Message-ID: <87r3tkqw94.fsf@gmx.us> (raw)
In-Reply-To: <874mqg32s4.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 20 Feb 2015 18:34:35 +0100")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> No this has the same issue as the Makefile. "It's not as easy as latex".
>
> Setting up a publishing project is easy and well documented.
So is Makefile.
>> I want *one* coherent file with all the necessary instructions, that can
>> be edited in different program from Emacs, and be easily compiled.
>>
>> E.g. I wrote syntax highlight for Org in texworks, but I also want to make
>> the "green button" work easily as latex without too many ugly hacks.
>
> Isn't a file local variable enough then?
It's not interpret in a batch call by default (which may be a feature that
is not wise to mess with).
> Also, what about the (let ((org-export-async-init-file ...))) suggested
> earlier?
How to I generalize this to a emacs --batch call from a random org file?
—Rasmus
--
The second rule of Fight Club is: You do not talk about Fight Club
next prev parent reply other threads:[~2015-02-20 18:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 11:35 External compilation Rasmus
2015-02-19 14:16 ` Sebastien Vauban
2015-02-19 14:47 ` Rasmus
2015-02-19 14:50 ` Sebastien Vauban
2015-02-20 12:07 ` [ox, patch] external compilation (was: External compilation) Rasmus
2015-02-20 16:10 ` [ox, patch] external compilation Nicolas Goaziou
2015-02-20 16:24 ` Rasmus
2015-02-20 17:34 ` Nicolas Goaziou
2015-02-20 18:21 ` Rasmus [this message]
2015-02-20 19:01 ` Nicolas Goaziou
2015-02-20 19:38 ` Rasmus
2015-02-21 9:35 ` Nicolas Goaziou
2015-02-21 11:35 ` Rasmus
2015-02-21 12:59 ` Nicolas Goaziou
2015-02-21 13:23 ` Rasmus
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=87r3tkqw94.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).