From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-user@gnu.org, Matt Wette <matt.wette@gmail.com>
Subject: Re: Starting a GNU Guile awesome list
Date: Sun, 8 Nov 2020 18:09:00 +0100 [thread overview]
Message-ID: <148b42ad-699e-4782-1d44-a94f14fe86c6@posteo.de> (raw)
In-Reply-To: <87y2kbybqo.fsf@elephly.net>
Hi Ricardo!
Thanks for your reply. I've not gotten around to trying this yet.
I was hoping for a solution, which could use Elisp in one part of the
makefile and bash in another part of the makefile. I seem to remember a
blog post somewhere, in which someone explained how to use various
things as shells in makefiles, but I have lost the link to it and could
not find it again. I also do not remember, whether that was multiple
different things as shell in one makefile, or in separate files.
For example I would like to use Elisp for the Emacs stuff and Bash for
removing files.
However, in the meantime I figured out, that I could simply mark
something as .PHONY when I do not care about its output already being
there or when it has no output.
At some point I need to learn more about makefiles again. For now I
think my makefile knowledge is only basic.
Thanks,
Zelphir
On 10/12/20 12:33 PM, Ricardo Wurmus wrote:
> Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
>
>>>> ~~~~
>>>> $ 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?
>> Yes : ) But that is the problem: How can I add a clean step, even though
>> I am using Emacs as shell? Or can I switch shell for one command?
> Try this elisp snippet:
>
> (call-process "/bin/rm" nil nil nil "the-file-to-delete")
>
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2020-11-08 17:09 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
2020-10-11 23:39 ` Zelphir Kaltstahl
2020-10-12 10:33 ` Ricardo Wurmus
2020-11-08 17:09 ` Zelphir Kaltstahl [this message]
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=148b42ad-699e-4782-1d44-a94f14fe86c6@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
--cc=rekado@elephly.net \
/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).