From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode@gnu.org
Subject: Re: emacs build command for org-files
Date: Mon, 27 Jan 2020 08:33:01 -0500 [thread overview]
Message-ID: <m2a76910tu.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <m1lfpt71qi.fsf@nobis-it.eu>
Stefan Nobis <stefan-ml@snobis.de> writes:
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> Hi everyone,
>
>> This is only semi-on-topic. I am looking for something like M-x compile for
>> my org-files, but I don't want it to necessarily use Makefiles. I am
>> looking for suggestions of existing solutions to this, or thoughts on how
>> to implement this.
>
> This may not be the solution you are looking for, but maybe a good
> source of ideas:
>
> https://github.com/doublep/eldev
Thanks for this tip. This is the kind of thing I was hoping this thread
would unearth. This seems kind of like rake from ruby, where the build
scripts are written in the language you are building from. That is more
aligned with what I am trying to do here.
>
> Another idea: Just use a (configurable) function name or source block
> name to look for in a document. Then some magic function (say
> org-compile-document) can look for a custom function/block inside the
> document (e.g. look for a marked source block) and execute it, if
> found. If no custom function/block is found, some default action will
> be executed (e.g. ask user what to do, run pre-configured default
> export action etc.).
This is what I do now. I thought (hoped?) maybe someone else had worked
out something similar, and had a better idea.
--
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:[~2020-01-27 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 18:10 emacs build command for org-files John Kitchin
2020-01-26 19:38 ` briangpowell .
2020-01-26 20:05 ` John Kitchin
2020-01-26 21:13 ` briangpowell .
2020-01-27 15:53 ` John Kitchin
2020-01-27 17:38 ` Jack Kamm
2020-01-27 19:13 ` John Kitchin
2020-01-27 8:16 ` Stefan Nobis
2020-01-27 13:33 ` John Kitchin [this message]
2020-01-27 12:40 ` Neil Jerram
2020-01-27 13:16 ` John Kitchin
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=m2a76910tu.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.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).