I sent a mail to the author of (term ansi-color), but seems the emal-address was invalid. Well, anyway, to the reason mentioned above, I think it's enough.
New implementation works now, I'll have some tests before release. Suggestions are welcome ;-) https://github.com/NalaGinrut/guile-colorized/tree/upstream On Tue, Dec 11, 2012 at 10:31 AM, Nala Ginrut <nalagin...@gmail.com> wrote: > On Mon, 2012-12-10 at 22:42 +0100, Ludovic Courtès wrote: >> Hi, >> >> Nala Ginrut <nalagin...@gmail.com> skribis: >> >> > Since (term ansi-color) code is small one, except for the comment, do we >> > still need to ask him for integration? IMO, we just borrowed something >> > interfaces from his code. >> >> Well yes, the color table itself is public data, not even copyrightable >> per se. >> >> > Another question: >> > I'll try to patch the colorized into 'pretty-print' now, but is it >> > expected? Or just leave it as a independent module? Which is the proper >> > way for the maintainer? >> >> Instead of patching (ice-9 pretty-print) specifically for your purposes, >> perhaps you could instead make it more generally extensible, in a way >> that would be useful for your use case but not only? >> > > I think (ice-9 colorized) is enough for colored-REPL purpose, of course, > with Daniel's 'option-REPL-printer' patch. Besides, it'll provide other > methods of coloring for the users. > > But the opinion to patch to 'pretty-print' also has a reason: if not, > we'll keep another version of 'list/vector/array' printers. And the > output indent may be different from 'pretty-print'. Some guys may think > it's interesting, but others maybe not. > > hmm... > >> (I first need to look at the other threads on this topic...) >> >> Thanks, >> Ludo’. > >
