From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Ricardo Wurmus <rekado@elephly.net>, Marius Bakke <mbakke@fastmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: change to the wrap-program procedure (was: core-updates, let’s go!)
Date: Tue, 2 Jan 2018 19:12:20 +0100 [thread overview]
Message-ID: <138af4ac-f1de-168f-c3a8-284769a32396@crazy-compilers.com> (raw)
In-Reply-To: <87mv1yajv3.fsf@elephly.net>
Am 31.12.2017 um 18:27 schrieb Ricardo Wurmus:
> There’s also a change to the wrap-program procedure that does without
> the shell wrappers and instead prepends a short Guile program, which is
> read as a comment in the target language. It’s better to play with this
> in the next core-updates cycle.
I assume, this is what we discussed in
<https://lists.gnu.org/archive/html/guix-devel/2017-11/msg00041.html>.
I just wonder whether this will keep the encoding-lines in place, like
these:
#!/usr/bin/python
# -*- coding: latin-1 -*-
from __future__ import print_function
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2018-01-02 18:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 10:27 core-updates, let’s go! Ludovic Courtès
2017-12-31 10:32 ` Efraim Flashner
2017-12-31 11:14 ` Danny Milosavljevic
2017-12-31 12:20 ` Danny Milosavljevic
2017-12-31 15:07 ` Marius Bakke
2017-12-31 17:27 ` Ricardo Wurmus
2018-01-02 18:12 ` Hartmut Goebel [this message]
2018-01-02 19:01 ` change to the wrap-program procedure (was: core-updates, let’s go!) Ricardo Wurmus
2018-01-02 19:19 ` change to the wrap-program procedure Hartmut Goebel
2018-01-02 20:47 ` Ricardo Wurmus
2017-12-31 14:44 ` core-updates, let’s go! Marius Bakke
2018-01-01 17:12 ` Ludovic Courtès
2018-01-01 19:08 ` Efraim Flashner
2018-01-03 18:35 ` Leo Famulari
2018-01-03 20:06 ` Leo Famulari
2018-01-03 19:34 ` Leo Famulari
2018-01-18 3:50 ` Leo Famulari
2018-01-20 0:51 ` core-updates: SELinux Leo Famulari
2018-01-28 12:32 ` Ricardo Wurmus
2018-01-20 20:57 ` core-updates, let’s go! Kei Kebreau
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=138af4ac-f1de-168f-c3a8-284769a32396@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.