Re: [screen-devel] couple of mac building issues, patch for one

[Micah Cowan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Scogland wrote:
> Hi,
> 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)

The patch doesn't look appropriate to me. Perhaps an explicit header
check in configure.in would be better?

> 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.

I've copied the screen-users list for this one (please send any
followups on this issue to the support list only).

Are you running screen within another screen? If not, telling screen
that the host term is screen-256color-bce, is equivalent to lying to it,
and can't be supported.

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer,
and GNU Wget Project Maintainer.
http://micah.cowan.name/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIY9FO7M8hyUobTrERAvMjAKCK0qm6C0hTQ7tTc5+9KE0m5Gf2XgCfbg48
HNKSMKchungXQSkS8Vva3xk=
=5qW9
-----END PGP SIGNATURE-----