On Fri, Jun 27, 2008 at 8:54 AM, Tom Scogland <[EMAIL PROTECTED]> wrote: > On Fri, Jun 27, 2008 at 8:18 AM, Christian Ebert <[EMAIL PROTECTED]> wrote: >> * Tom Scogland on Thursday, June 26, 2008 at 07:21:55 -0500 >>> I've been a screen user for a few years on linux, but when switching >>> to osx as my primary os not too long ago (long story...) I found the >>> current development versions wont build. The issue was just a #ifdef >>> that was checking the wrong item, patch attached. (sorry if this isn't >>> the right place, given recent activity it seemed like the best idea) >> >> I always apply attached patch that apple apparently uses for its >> shipped screen w/o probs. >> >> <http://www.opensource.apple.com/darwinsource/tarballs/other/screen-11.tar.gz> > Interesting, and thanks for forwarding this along, I'll try these out. > I was building from source since I've gotten used to having vertical > splits, and didn't know about the patches, should be very helpful. =)
Sorry for double post like this, but these seem to work well, and your patch against pty.c does seem more reasonable than mine if the check was not in fact a typo. Thanks again! >> >>> There is one other issue however that I'm having much worse trouble >>> tracking down. On osx if I specify that screen should use >>> screen-256color-bce as its TERM, it fails back to vt100 and all >>> features disappear, once this happens I can't change screen's internal >>> term through ^a:term it just sticks there. As a temporary measure I'm >>> having it use xterm-256color, but I would like to find/fix the issue, >>> if anyone knows where I might look for that it would be very helpful. >>> Oh, and that term value works fine on linux and the terminfo file is >>> in the path in 3 seperate places... so it shouldn't be a path issue. >> >> FWIW, I can't reproduce this. Is this within Terminal.app? >> Because there nsterm family is recommended -- only wsorks up to >> nsterm-16color though with recent ncurses. >> >> Within X11 xterm both xterm-256color and xterm-256color-bce work >> for me -- personally I prefer w/o bce as in some apps (mutt) the >> drawing of menu bars do not span the whole width. > > It's in X11.app's xterm, xterm-256color works fine as a containing > terminal, but when I tell screen to tell its children it is a > screen-256color or screen-256color-bce, as in "term > screen-256color-bce" in .screenrc, that's when things go horribly > wrong. It seems like it can't find the terminfo description for that > terminal, but none of my other apps have an issue finding it... very > odd. xterm-256color as screen's value seems to be working ok for now, > so I guess I can leave it that way, it just seems off to me that it > works fine under linux and has such bad results in osx. > >> >> This is on MacOS 10.4.11. For Leopard I don't know. >> >> c >> -- >> Was heißt hier Dogma, ich bin Underdogma! >> [ What the hell do you mean dogma, I am underdogma. ] >> >> _F R E E_ _V I D E O S_ -->> http://www.blacktrash.org/underdogma/ >> > > > > -- > -N > AKA:Tom Scogland > I am enough of an artist to draw freely upon my imagination. > Imagination is more important than knowledge. Knowledge is limited. > Imagination encircles the world. > -Albert Einstein > -- -N AKA:Tom Scogland I am enough of an artist to draw freely upon my imagination. Imagination is more important than knowledge. Knowledge is limited. Imagination encircles the world. -Albert Einstein
