$ echo $TERM xterm-color $ echo $COLORTERM $
I'm using iTerm.app Build 0.9.6.20090415 The same error msg is also reported on OS X's default Terminal.app I'm not familiar with these variables, but I tried to set COLORTERM=y, no luck. By setting TERM=ansi or linux, I got yi-darwin-i386: user error (Terminal does not define required capability "smcup") Thanks, -Wen On Aug 30, 1:43 pm, "Corey O'Connor" <coreyocon...@gmail.com> wrote: > On Sat, Aug 29, 2009 at 10:39 PM, Wen Pu<dexte...@gmail.com> wrote: > > > Hi Corey, > > > I got this on my Mac (iTerm.app): > > > yi-darwin-i386: user error (Terminal does not define required > > capability "cnorm") > > That capability should be defined. Something is probably wrong in how > vty determines the terminfo database to use. I haven't tested on OS X > at all yet. > > Can you tell me the value of the TERM and COLORTERM environment variable? > > Cheers, > Corey > > > On Aug 29, 12:47 pm, "Corey O'Connor" <coreyocon...@gmail.com> wrote: > >> On Fri, Aug 28, 2009 at 5:02 PM, Simon Michael<si...@joyful.com> wrote: > >> > Yes, I think mtl and parsec 2 are both still preferred and used by the > >> > majority of packages and the Haskell Platform. > >> > And yes if you want to support alternate dependencies a cabal flag that > >> > also sets a cpp flag is the way to go, I do it > >> > in hledger.cabal. > > >> OK. I've updated vty in darcs to use mtl and support both parsec 2 and > >> parsec 3. Attached is the updated yi patch that accounts for some > >> other changes as well. > > >> Let me know if there are any further issues. :-D > > >> Thanks! > > >> vty_4_0_0_support.dpatch > >> 57KViewDownload > > --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
