FS#18673 - [screen] hardstatus string does not persist on new windows after "^a+c"

Attached to Project: Arch Linux
Opened by vhp (vhp) - Sunday, 14 March 2010, 01:08 GMT
Last edited by Jan de Groot (JGC) - Sunday, 14 March 2010, 18:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Screen(1) hardstatus string does not persist on new windows after a "^a+c", and only remains attached to the original window. If one were to create a new window and go to the next or previous window, the hardstatus line will not be set on the newly created window. Though if one were to go back to the original window the hardstatus line will persists. Such is not a problem in the versions from the Debian/Ubuntu repositories or when building from source. The hardstatus options I have set in my .screenrc are below and very basic:

hardstatus on
hardstatus alwayslastline
hardstatus string 'temp'


Additional info:
* Version: Screen version 4.00.03 (FAU) 23-Oct-06
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 14 March 2010, 18:22 GMT
Reason for closing:  Not a bug
Additional comments about closing:  2010-03-14: A task closure has been requested. Reason for request: Please just delete this bug. Thank you.
Comment by Allan McRae (Allan) - Sunday, 14 March 2010, 01:46 GMT
I can not replicate on i686.

Where are you running screen from? What do you have set for $TERM (both in and out of screen)?
Comment by vhp (vhp) - Sunday, 14 March 2010, 03:00 GMT
I'm using amd64, and running screen from inside of a normal bash xterm shell. I only get the problem when I set the $TERM in screen to "screen-256color", I don't get the problem if screen's $TERM is set to xterm. Though I will say that the problem does not occur when $TERM is set to screen-256color in different versions of screen, like if one were to build screen from its source or from the debian distro's.

I do apologize for not being as clear as I should have been.
Comment by Allan McRae (Allan) - Sunday, 14 March 2010, 03:05 GMT
What do you mean building from source? Just rebuilding the package using ABS and makepkg? Or building manually? If the later, what configure options are you using?
Comment by vhp (vhp) - Sunday, 14 March 2010, 03:12 GMT
Just configuring, making and then an install, all from the most recent version here ftp://ftp.gnu.org/gnu/screen/. No special options, just the default.
Comment by Allan McRae (Allan) - Sunday, 14 March 2010, 05:55 GMT
I tried xterm and various settings of TERM on i686 and x86_64 and still can not replicate... Can you work through the configure flags from the PKGBUILD and find which one appears to be causing the issue for you.

Loading...