From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Dmitry Alexandrov <dag@gnui.org>
Cc: guile-user@gnu.org
Subject: Re: Starting a GNU Guile awesome list
Date: Thu, 16 Jul 2020 21:01:17 +0200 [thread overview]
Message-ID: <87blkfuvwi.fsf@web.de> (raw)
In-Reply-To: <a6zzq21v.dag@gnui.org>
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
Dmitry Alexandrov <dag@gnui.org> writes:
> "Dr. Arne Babenhauserheide" <arne_bab@web.de> wrote:
>>>> In the case you will stick with Org, there at least should be a runnable build recipe (i. e. a Makefile).
>>
>> I’d like to cut this discussion short:
>>
>> https://notabug.org/ZelphirKaltstahl/awesome-guile/pulls/1/files
>
>> all: readme.md readme.texi readme.html
>> .INTERMEDIATE: .exported
>> readme.md readme.texi readme.html: .exported
>> .exported: readme.org
>> HOME=$$(dirname $$(realpath "$<")) emacs -Q --batch "$<" --exec "(require 'ox-md)" -f org-md-export-to-markdown -f org-html-export-to-html -f org-texinfo-export-to-texinfo -f kill-emacs
>
> Alternatively, without reliance on implicit behaviour (setting HOME in order to get an expected filename??):
No, I actually set home, because I‘m used to having a custom emacs setup
there. With the -Q you can leave it out.
> #!/usr/bin/make -f
>
> SHELL := emacs
> .SHELLFLAGS := --quick --batch --eval
>
> orgs := $(wildcard *.org)
> objs := $(orgs:.org=.md) $(orgs:.org=.texi)
>
> .PHONY: all
> all: $(objs)
>
> .ONESHELL:
> %.md %.texi: %.org
> (with-temp-buffer
> (require 'ox-md)
> (require 'ox-texinfo)
> (when (insert-file-contents "$<")
> (org-mode)
> (org-export-to-file 'md "$*.md")
> (org-export-to-file 'texinfo "$*.texi")))
Wow, using emacs as shell is quite a trick to get full elisp in
makefiles. Nice!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next prev parent reply other threads:[~2020-07-16 19:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 21:19 Starting a GNU Guile awesome list Zelphir Kaltstahl
2020-07-13 21:56 ` Jack Hill
2020-07-13 22:56 ` Aleix Conchillo Flaqué
2020-07-14 23:26 ` Zelphir Kaltstahl
2020-07-14 9:00 ` Dmitry Alexandrov
2020-07-14 21:23 ` Zelphir Kaltstahl
2020-07-15 6:32 ` Dr. Arne Babenhauserheide
2020-07-16 8:47 ` Dmitry Alexandrov
2020-07-16 19:01 ` Dr. Arne Babenhauserheide [this message]
2020-10-10 12:31 ` Zelphir Kaltstahl
2020-10-10 13:14 ` Matt Wette
2020-10-11 0:57 ` Zelphir Kaltstahl
2020-10-11 19:51 ` Ricardo Wurmus
2020-10-11 23:39 ` Zelphir Kaltstahl
2020-10-12 10:33 ` Ricardo Wurmus
2020-11-08 17:09 ` Zelphir Kaltstahl
2020-11-08 18:55 ` Paul Smith
2020-12-05 18:15 ` Zelphir Kaltstahl
2020-07-15 6:36 ` Dr. Arne Babenhauserheide
2020-07-15 21:14 ` Zelphir Kaltstahl
2020-07-15 22:40 ` Dr. Arne Babenhauserheide
2020-07-16 9:18 ` A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list) Dmitry Alexandrov
2020-07-16 18:56 ` Dr. Arne Babenhauserheide
2020-07-16 18:58 ` Dr. Arne Babenhauserheide
2020-07-16 20:47 ` Zelphir Kaltstahl
2020-07-16 22:55 ` Vladimir Zhbanov
2020-07-16 23:05 ` Vladimir Zhbanov
2020-07-17 0:20 ` John Cowan
2020-07-17 6:43 ` Dr. Arne Babenhauserheide
2020-07-14 14:14 ` Starting a GNU Guile awesome list Dr. Arne Babenhauserheide
2020-07-15 21:24 ` Zelphir Kaltstahl
2020-07-15 22:29 ` Dr. Arne Babenhauserheide
2020-07-14 16:37 ` Taylan Kammer
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blkfuvwi.fsf@web.de \
--to=arne_bab@web.de \
--cc=dag@gnui.org \
--cc=guile-user@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.
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).