From: Ricardo Wurmus <rekado@elephly.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user@gnu.org, Matt Wette <matt.wette@gmail.com>
Subject: Re: Starting a GNU Guile awesome list
Date: Sun, 11 Oct 2020 21:51:04 +0200 [thread overview]
Message-ID: <871ri4zglz.fsf@elephly.net> (raw)
In-Reply-To: <3bbb1573-eff8-975f-bae0-4d305d84e09f@posteo.de>
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
> Hello Matt,
>
> On 10/10/20 3:14 PM, Matt Wette wrote:
>>
>>
>> On 10/10/20 5:31 AM, Zelphir Kaltstahl wrote:
>>>
>>>> #!/usr/bin/make -f
>>>>
>>>> SHELL := emacs
>>>> .SHELLFLAGS := --quick --batch --eval
>>>>
>>>>
>>
>> Maybe try this:
>>
>> #!/usr/bin/make -f -
>>
>> with the added dash.
>
> This does not seem to change anything:
>
> ~~~~
> #!/usr/bin/make -f -
>
> # use emacs as a shell, so that we can write emacs lisp code in here
> SHELL := emacs
> # set some flags for emacs
> .SHELLFLAGS := --quick --batch --eval
>
> # all org mode files will be converted
> # orgs := $(wildcard *.org)
> # only the list.org file will be converted
> orgs := list.org
> objs := $(orgs:.org=.md) $(orgs:.org=.texi) $(orgs:.org=.html)
>
> .PHONY: all
> all: $(objs)
>
> .PHONY: clean
> clean:
> /bin/rm --verbose *.html *.md *.texi || true;
>
> # in here comes the shell specific code
> .ONESHELL:
> %.html %.md %.texi: %.org
> (with-temp-buffer
> (require 'ox-md)
> (require 'ox-texinfo)
> (require 'ox-html)
> (when (insert-file-contents "$<")
> (org-mode)
> (org-export-to-file 'md "$*.md")
> (org-export-to-file 'texinfo "$*.texi")
> (org-export-to-file 'html "$*.html")))
> ~~~~
>
> ~~~~
> $ make clean
> /bin/rm --verbose *.html *.md *.texi || true;
> Symbol’s value as variable is void: /bin/rm
> make: *** [Makefile:19: clean] Error 255
> ~~~~
Well, isn’t that expected as you’re using Emacs as a shell?
--
Ricardo
next prev parent reply other threads:[~2020-10-11 19:51 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
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 [this message]
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=871ri4zglz.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
--cc=zelphirkaltstahl@posteo.de \
/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).