From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Neil Jerram <neiljerram@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: emacs build command for org-files
Date: Mon, 27 Jan 2020 08:16:33 -0500 [thread overview]
Message-ID: <m2eevl11la.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <CAKuG=vshFoZZCSZdJWsYjRLa5uUFaMdBU0QjXYkyVbwCPzBJjQ@mail.gmail.com>
Neil Jerram <neiljerram@gmail.com> writes:
> On Sun, 26 Jan 2020 at 18:11, John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>
>> 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.
>>
>> Actually, if it was possible to get M-x compile to run an elisp function
>> instead of a make file, it might be all I need, but it looks like it runs
>> shell commands.
>>
>
> So how about typing "M-: <elisp>" instead of "M-x compile" ? Why involve
> other layers when Emacs can directly evaluate elisp?
It is just a reflection of how long some of the build blocks are. They
frequently let-bind variables and functions to achieve some particular
goal for the specific project. Since it is a one-time block, I don't
usually make it a function, and the code exists in a src block. "M-:"
isn't convenient for me in this scenario.
>
> Best wishes,
> Neil
--
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
prev parent reply other threads:[~2020-01-27 13:16 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
2020-01-27 12:40 ` Neil Jerram
2020-01-27 13:16 ` John Kitchin [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=m2eevl11la.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=neiljerram@gmail.com \
/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).