Hello Andreas, I realize now that this is probably the trade-off you mentioned earlier regarding the workaround.
Could you expound on what you meant by "... the display backend is now also configurable."? Thanks and regards, Emil On Fri, Nov 8, 2013 at 7:26 AM, Emil Belardo <[email protected]> wrote: > Hello Andreas, > > This may or may not be related to the fix for line filling, but I notice > that when I try to apply my custom theme now, the settings don't seem to > take anymore. Instead, I get a minimal color theme (see attached > screenshot). > > Applying any pre-existing theme still works, though. > > I think the reason is because I was using xterm color number codes (ex: > "h1" for red) instead of color names (ex: "dark red") in my theme script. > > I can switch to using color names instead, no worries. Just wanted you to > know what I encountered. > > I am attaching my custom theme for reference. > > Thanks and regards, > Emil > > > On Fri, Nov 8, 2013 at 6:38 AM, Emil Belardo <[email protected]> wrote: > >> Hello Andreas, >> >> I realized my mistake after sending out my email. Ouch. >> >> Okay, so this time I pulled down the *pudb source* from git and tested >> that against tmux (1.8) with good results (see attached screenshot)! >> >> The interface is so comfortable to look at now in tmux :-) >> >> Thank you for your efforts! >> >> Regards, >> Emil >> >> >> On Fri, Nov 8, 2013 at 6:21 AM, Emil Belardo <[email protected]> wrote: >> >>> Hello Andreas, >>> >>> Thanks for the information! I would be happy to test the workaround. >>> >>> I pulled down the source from git and tested it against pudb in tmux >>> (1.8) but still got the same result (screenshot attached). >>> >>> I am including my steps below in case I missed a step somewhere. >>> >>> # uninstall current urwid >>> pip uninstall urwid >>> >>> # install urwid from source >>> cd ~/code >>> git clone https://github.com/wardi/urwid >>> cd urwid >>> python setup.py install --prefix=/opt/local/python27 >>> >>> # test if curses is available in python >>> python >>> >>> import curses >>> >>> # within tmux, check value of $TERM >>> tmux >>> echo $TERM >>> >>> screen-256color >>> >>> # within tmux, test pudb >>> python -m pudb.run 05-17.py >>> >>> Let me know if I missed anything. Also, may I know the changeset number >>> or where in the code the workaround is located? That could help me play >>> around a bit more. >>> >>> Thanks and regards, >>> Emil >>> >>> >>> On Thu, Nov 7, 2013 at 9:41 PM, Andreas Kloeckner < >>> [email protected]> wrote: >>> >>>> Emil Belardo <[email protected]> writes: >>>> >>>> > Hello pudb, >>>> > >>>> > Congratulations on an excellent application! >>>> > >>>> > Having said that, I am emailing to report a slight issue regarding >>>> pudb in >>>> > tmux. When I launch pudb in tmux, the background color of the title >>>> bars >>>> > seems to cut off at the last text in the bar instead of stretching to >>>> the >>>> > rightmost end (see attached screenshot). >>>> > >>>> > Has anyone else noticed this? Could there possibly be a workaround? >>>> > >>>> > If not, I suppose I can live with it. >>>> >>>> That's an urwid bug: >>>> >>>> https://github.com/wardi/urwid/issues/33 >>>> >>>> (as you can tell, that issue has been annoying me, too) >>>> >>>> I've just implemented a workaround that falls back to the urwid curses >>>> display driver if it deems doing so appropriate. (the display driver is >>>> set to "auto", $TERM doesn't start with "xterm" and curses is >>>> available.) Since there's a trade-off there (the curses backend doesn't >>>> support fancy highlighting, for instance), the display backend is now >>>> also configurable. >>>> >>>> This is now in git. I'd much appreciate if you (and whoever else reads >>>> this) could give this code a whirl and see if works. If so, I'll push >>>> out a new version. >>>> >>>> Andreas >>>> >>> >>> >> >
_______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
