Hi,
I put RPMS of screen-4.0.1 on my people.redhat.com account. You can use yum:
http://people.redhat.com/lhh/fedora
Or, download the packages directly:
http://people.redhat.com/lhh/fedora/screen-4.0.1-0.1.i386.rpm http://people.redhat.com/lhh/fedora/screen-4.0.1-0.1.src.rpm
The major difference is screen's lack of needing backspace bindings.
NOTE NOTE NOTE: If you test this package, you must also comment out the "stty erase `tput kbs`" line from your shell's rcfile. Tcsh users, I am told, do not need to do this.
Additionally, you may have to remove the backspace key binding from /etc/screenrc or ~/.screenrc (If RPM saves your old configuration...)
The goal here is to remove all of the workaround we put in to make screen work properly WRT backspace/del. In theory, 4.0.1 no longer needs them.
On Fri, Oct 31, 2003 at 08:51:25AM -0500, Lon Hohberger wrote:
NOTE NOTE NOTE: If you test this package, you must also comment out the "stty erase `tput kbs`" line from your shell's rcfile. Tcsh users, I am told, do not need to do this.
Ok, I've done this,
Whenever I start a brand new screen session (this does not happen when attaching to a previous session), I get some kind of error message flashing by the title bar on my terminal window (with both xterm and gnome-terminal). It flashes by too quickly for me to comprehend the entire error message.
Wait, let me try again from a Mac OS X "Jaguar" Terminal, and see if I can copy-and-paste... Got it! Here's the message:
/etc/screenrc: bind: character, ^x, or (octal) \032 expected.
This is in fact the new /etc/screenrc from your new package. I did 'rpm -e screen' and made sure there was no /etc/screenrc, before installing your new package, just to make sure.
Other than this message, things seem fine so far!
-Barry K. Nathan barryn@pobox.com
On Fri, 2003-11-07 at 02:53, Barry K. Nathan wrote:
/etc/screenrc: bind: character, ^x, or (octal) \032 expected.
Thanks for that tidbit - I'd previously been unable to capture that message, but it is a known bug (my coworkers have reported it too). It seems to be a bug in the default screen-4.0.1 screenrc file; I'll ask the developer.
Other than this message, things seem fine so far!
Great! I'll work on the one above as well as try and cut down on the number of unnecessary patches we include.
-- Lon
-
Barry K. Nathan -
Lon Hohberger