On Tue, Sep 1, 2009 at 6:40 PM, Wen Pu<dexte...@gmail.com> wrote: > > I tried on my Terminal.app, it works well, but I still has problem on > iTerm.app ... > > The color of the first line in dired buffer is back (grey), but only > the first line. > The color of directory (blue) and marks (green, red) are still > missing, so does the high lighted search terms. > Does this only happen on my iTerm?
hm. What theme are you using for yi? And what is your display profile for iTerm? Everything appears equivalent to yi w/ vty 3 on iTerm using the darkBlue theme on my machine. My iTerm is the latest installed by the auto-updater and is using the default "light background" display profile. I've also tried the "dark background" display profile with success. This is what I see: http://www.flickr.com/photos/goawaystupidai/3879471569/ This may be a bug in the vty 4 update for yi and not vty specifically. yi should not depend on the terminal's default colors for any styling done. Every display attribute used by yi should have a concrete color for the foreground and background. Otherwise the final display will depend on the terminal's "default" colors. Which can not easily or portably be determined or modified, as far as I know. I'll look into how the dired styles are defined for yi and make sure there is no chance a "default" color is used. Last but not least: Try running through vty/test/interactive_terminal_test.hs by cd'ing to test and running "make interactive_terminal_test". If it builds, which the makefile is still picky about, all checks should pass on iTerm. Cheers, Corey O'Connor > On Sep 1, 2009, at 6:28 PM, Corey O'Connor wrote: > >> >> OK! One last test before release. If nobody finds a show-stopping bug >> in the latest vty from darcs then I'll call it done and push it out. >> >> Recent changes: >> - clamps requested display colors to those supported by the >> terminal. For instance, if the terminal does not support the bright >> colors just the normal intensity colors will be used. >> - Does not assume the existence of the sgr capability. Tries to >> use the enter/exit display mode caps if possible. >> - Does not assume the existence of the smcup/rmcup capability. >> - Faster! (and can be optimized yet further) >> - Only changed lines will be updated. >> - Only the minimum sequence of control strings are output for >> display style changes. >> >> Terminals I've tested as working (at least as good as possible): >> - xterm (under OS X and Ubuntu) >> - gnome-terminal >> - konsole >> - screen (under OS X and Ubuntu) >> - linux vty (The interface you get w/o X11.) >> - Terminal.app >> - iTerm.app >> - mlterm >> - rxvt >> >> If I'm missing a popular terminal let me know. >> >> Thanks! >> -Corey O'Connor >> >> >> >> On Mon, Aug 31, 2009 at 3:09 PM, Corey >> O'Connor<coreyocon...@gmail.com> wrote: >>> -Corey O'Connor >>> >>> >>> >>> On Mon, Aug 31, 2009 at 3:08 PM, Corey O'Connor<coreyocon...@gmail.com >>> > wrote: >>>> Minor change: Supporting the latest vty darcs changes. Does not >>>> resolve issues with dired mode on iTerm yet. >>>> >>>> -Corey O'Connor >>>> >>>> >>>> >>>> On Sun, Aug 30, 2009 at 4: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 -~----------~----~----~----~------~----~------~--~---
