From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@infotropique.org>
Cc: 28744-done@debbugs.gnu.org
Subject: bug#28744: guile-colorized
Date: Sun, 08 Oct 2017 21:51:08 +0200 [thread overview]
Message-ID: <87po9xbeqb.fsf@gnu.org> (raw)
In-Reply-To: <20171008103637.6vwpp5s75ixvbemz@abyayala> (ng0@infotropique.org's message of "Sun, 8 Oct 2017 10:36:37 +0000")
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
Hi!
ng0 <ng0@infotropique.org> skribis:
> Colors for your REPL.
>
> In the light of recent github mismatches:
> should this use the git checkout instead?
I think it’s (still) fine this way.
> From d5160f7e3ca160dd6ee9336770fdf2d6dc7b279f Mon Sep 17 00:00:00 2001
> From: ng0 <ng0@infotropique.org>
> Date: Sun, 8 Oct 2017 10:30:39 +0000
> Subject: [PATCH] gnu: Add guile-colorized.
>
> * gnu/packages/guile.scm (guile-colorized): New variable.
Pushed with the slight simplification below.
Thank you!
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 823 bytes --]
diff --git a/gnu/packages/guile.scm b/gnu/packages/guile.scm
index caecd2b6b..e32ca84a7 100644
--- a/gnu/packages/guile.scm
+++ b/gnu/packages/guile.scm
@@ -1995,12 +1995,9 @@ It has a nice, simple s-expression based syntax.")
(guild (string-append (assoc-ref inputs "guile")
"/bin/guild")))
;; The original 'make install' is too primitive.
- (mkdir-p module-dir)
- (mkdir-p language-dir)
;; copy the source
- (copy-file "ice-9/colorized.scm"
- (string-append language-dir "/colorized.scm"))
+ (install-file "ice-9/colorized.scm" language-dir)
;; compile to the destination
(compile-file "ice-9/colorized.scm"
prev parent reply other threads:[~2017-10-08 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 10:36 [bug#28744] guile-colorized ng0
2017-10-08 19:51 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po9xbeqb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28744-done@debbugs.gnu.org \
--cc=ng0@infotropique.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.
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.