-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (My mailer is doing the quoting backwards again)
Tom Scogland wrote: > On Thu, Jun 26, 2008 at 12:26 PM, Micah Cowan <[EMAIL PROTECTED]> wrote: > 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? > >> Admittedly it might be, but the patch seemed appropriate as 'SVR4' >> rather than 'HAVE_SVR4_PTYS' is used to check all 3 other inclusions >> of that header. Thus my assumption was that it was a typo in pty.c >> that the wrong define was used, and thus a reasonable solution to make >> it match the 3 in process.c, screen.c and tty.c. You're right, of course: I was informed of this later, and sure enough, you're right. I like the direct check better, but I have to admit that "inappropriate" was a poor word to describe it. At least for the meantime, it's probably preferable to maintain consistency; we can always change it later. > 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. > >> No, I'm telling it the host term is xterm-256color and in screenrc or >> on the command line telling screen that it should set its internal >> term variable, used for TERM in all shells run inside of screen, >> should be screen-256color-bce. Sorry that apparently wasn't clear, >> but the issue is that when setting the term to that value, which is >> normally perfectly valid, causes it to lock me into vt100 for the >> remainder of the session. The closest thing I have to a solution >> right now is telling everything running in screen that screen is a 256 >> color xterm, which is equivalent to lying to them as you put it. No, you were clear enough, it was me who was befuddled, sorry. I was thinking screen's "term" command works like vim's. You mention that the terminfo file is on the path in 3 separate places; what are those places? Where is terminfo looking when it finds (say) the xterm entry (look at the top line of the output from "infocmp xterm"). Have you tried setting the TERMINFO env variable? - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer, and GNU Wget Project Maintainer. http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIa6h27M8hyUobTrERAmvMAJ97IEoI2dVRb7cVJrvsrF4wrUkbVQCdG4WB swh5hAQNxcxzNpw62Dpdd3I= =brJZ -----END PGP SIGNATURE----- _______________________________________________ screen-users mailing list screen-users@gnu.org http://lists.gnu.org/mailman/listinfo/screen-users
