Can you clarify which overlays are not visible? I suspect the vivid/bright colors will not be visible. The previous version of Vty assumed 16 color support: 8 standard colors and 8 bright colors. The control strings used did not depend on what terminfo reported. Xterm would accept control strings for xterm-16color even if the terminal was xterm or xterm-color. Which, according to terminfo, support only 8 colors. Currently Vty is more "accurate" than the previous version. If the terminal reports only 8 colors then 8 colors are possile; no more. The only way around this is to assure TERM is set correctly.
Try setting TERM to xterm-256color before starting yi. If this corrects the overlays then the above hypothesis is correct. In Graphics/Vty/Terminal is the logic for selecting a terminal instance. I have considered extending this to "correcting" TERM in this case such that Vty behaves as before. (This is currently done for OS X) the risk is incorrectpy displaying overlays on xterm like terminals that only support 8 colors; which is probably worth it. Mashed together on a phone. On Aug 30, 2009, at 9:15 PM, Wen Pu <dexte...@gmail.com> wrote: > > Hmmm, seems the overlays in dired mode are no longer effective on VTY > 4. > > I can still see colors in haskell mode, but not in dired buffer. > Any idea? > > -Wen > > On Aug 30, 6:02 pm, "Corey O'Connor" <coreyocon...@gmail.com> wrote: >> I have adjusted how vty handles terminals on OS X. Terminal.app, >> iTerm.app and xterm via X11 all work as expected in my testing. Pull >> the latest vty patches from darcs, install, and then yi should work >> OK. >> >> Possible issues: >> - The last line in yi is displayed without the correct attributes? >> - iTerm displays bold in red? I think this is a feature of iTerm >> actually. >> - The standard xterm-color termcap on OS X is 8 colors only. vty >> does >> not adjust it's output to match. >> - termcaps from /sw/ appear to be incorrect? >> >> Also, iTerm.app supports the xterm-256color profile. For added color >> have iTerm set the TERM variable to xterm-256color. >> >> Cheers, >> -Corey O'Connor >> >> 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") >> >>> Anything wrong? >> >>> Thanks! >>> -Wen >> >>> 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 -~----------~----~----~----~------~----~------~--~---
