Date: Mon, 2 Oct 2000 20:57:33 -0700 From: Jamie Norwood <mistwolf@mushhaven.net> To: Dan Nelson <dnelson@emsphone.com> Cc: Otter <otterr@telocity.com>, freebsd-questions@FreeBSD.ORG Subject: Re: Raising PTYs Message-ID: <20001002205732.A29413@mushhaven.net> In-Reply-To: <20001002225555.C23329@dan.emsphone.com> References: <20001001210159.A17043@dan.emsphone.com> <HLEDJBJKDDPDJBMGCLPPOEIHCEAA.otterr@telocity.com> <20001002174100.A6585@mushhaven.net> <20001002224551.B23329@dan.emsphone.com> <20001002204859.A29344@mushhaven.net> <20001002225555.C23329@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 02, 2000 at 10:55:55PM -0500, Dan Nelson wrote: > In the last episode (Oct 02), Jamie Norwood said: > > I installed the latest ncurses (5.1) and the problem went away... So, > > for now, this is my recommendation. I have SecureCRT set to VT100 and > > my TERM variabl to vt100. Note screen 3.9.8 hard-sets it's termcap in > > your environment. > > Right; screen has always done this, since the terminal it presents to > subshells (true ANSI X3.64 with colors) is different from the terminal > you used to run it. I used to use screen on old z19 terminals so I > could run programs that hardcoded ANSI escape sequences in them. > What's important is that the TERM you have before you run screen > matches your terminal/emulator as closely as possible. So... Why did installing ncurses fix it? I don't entirely understand how this is working, or what can be done to fix it other than to use ncurses. I never had this problem with screen 9.5.x, and wouldn't have upgraded if I didn't need to recompile for more pty's. Jamie > > -- > Dan Nelson > dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001002205732.A29413>