[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Colorized REPL

From: Nala Ginrut
Subject: Re: [PATCH] Colorized REPL
Date: Thu, 06 Dec 2012 10:43:54 +0800

On Wed, 2012-12-05 at 19:19 +0800, Daniel Hartwig wrote:
> On 5 December 2012 18:27, Nala Ginrut <address@hidden> wrote:
> > I can understand this too. So your suggestion is to write a
> > (term ansi-color) compatible interface. I think it's easy to do.
> > But I'm afraid that Guile don't integrate (term ansi-color).
> In your code, one uses "(light-blue yellow)", and only some times as a
> list, where as in ansi-color the symbols are upper case and the names
> different, "RED ON-BLUE".  I am suggesting to use the same names for
> same things, so the interface is more-or-less compatible.

Agreed. ;-)

> > Or I should
> > copy (term ansi-color) into colorized.scm? It's not a big one, but is it
> > proper?
> I am not sure about the licensing there.  That module is copyrighted,
> though GPLv3+.  A merge /may/ require the original author to assign
> the copyright.
> Still, reusing it would be ideal, which is why I suggest to target
> this extension to guile-lib and avoid maintaining two sets of similar
> colour->ansi-string type functions.

Seems things gonna be a little complicated.
IMO, the perfect solution is to merge (term ansi-color) into (ice-9
colorized), and we reused the code, and the user can use colored string,
everyone is happy.

But if we need the original author to assign the copyright, I'm not sure
how long will it be. Last time I assigned the copyright took about one
month, since it's long way to send a hand-written assignment to USA.
Or I just request the original author to assign the copyright in the
Which one is right?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]