First, my apologies for posting about Linux in comp.os.linux.misc, but I
need a senior GNU Screen 5.x .screenrc config file programmer to sort
this mess out. When Screen 4.x jumped to Screen 5.x, it broke hardstatus strings and I've not gotten them to work correctly since. Last night I
spent 60 minutes on this without results. We all love breaking config
file changes, don't we?
On 2026-10-29 17:25, jayjwa wrote:
First, my apologies for posting about Linux in comp.os.linux.misc, but I
need a senior GNU Screen 5.x .screenrc config file programmer to sort
this mess out. When Screen 4.x jumped to Screen 5.x, it broke hardstatus
strings and I've not gotten them to work correctly since. Last night I
spent 60 minutes on this without results. We all love breaking config
file changes, don't we?
Just posting so that you know that people read your post, even if we
are engrossed in OT posts, but I'm not qualified to answer it. Sorry.
Not familiar with Screen; I use Tmux myself, but I don't touch the
status line.
On 2026-10-29, Carlos E.R. wrote:
On 2026-10-29 17:25, jayjwa wrote:
First, my apologies for posting about Linux in comp.os.linux.misc, but I >>> need a senior GNU Screen 5.x .screenrc config file programmer to sort
this mess out. When Screen 4.x jumped to Screen 5.x, it broke hardstatus >>> strings and I've not gotten them to work correctly since. Last night I
spent 60 minutes on this without results. We all love breaking config
file changes, don't we?
Just posting so that you know that people read your post, even if we
are engrossed in OT posts, but I'm not qualified to answer it. Sorry.
Not familiar with Screen; I use Tmux myself, but I don't touch the
status line.
(I was a bit confused as I expected this to be about a "hard" status
line, but seems to be a repurposing of the hard status line for
graphical terminal emulators?)
On 2026-10-30 02:25, Nuno Silva wrote:
On 2026-10-29, Carlos E.R. wrote:
On 2026-10-29 17:25, jayjwa wrote:
First, my apologies for posting about Linux in comp.os.linux.misc, but I >>>> need a senior GNU Screen 5.x .screenrc config file programmer to sort
this mess out. When Screen 4.x jumped to Screen 5.x, it broke hardstatus >>>> strings and I've not gotten them to work correctly since. Last night I >>>> spent 60 minutes on this without results. We all love breaking config
file changes, don't we?
Just posting so that you know that people read your post, even if we
are engrossed in OT posts, but I'm not qualified to answer it. Sorry.
Not familiar with Screen; I use Tmux myself, but I don't touch the
status line.
(I was a bit confused as I expected this to be about a "hard" status
line, but seems to be a repurposing of the hard status line for
graphical terminal emulators?)
Google AI: The screen command in Linux is a terminal multiplexer that
allows you to start a terminal session and then completely detach from
it. This leaves your processes running in the background, making it an invaluable tool for executing long-running tasks over SSH without
worrying about network drops or accidental disconnections.
Ie, similar to tmux. I gather you can customize the status line.
Set 'nothink' mode.Google AI: The screen command in Linux is a terminal multiplexer that
allows you to start a terminal session and then completely detach from
it. This leaves your processes running in the background, making it an
invaluable tool for executing long-running tasks over SSH without
worrying about network drops or accidental disconnections.
Ie, similar to tmux. I gather you can customize the status line. Right...it's the *doing* part I'm having an issue with.
Ask it what is a hard status line, to see if it gets that part right :-)
/set nothink
A **GNU `screen` hardstatus** line is a special configurationWhat is a GNU Screen hardstatus line?
... hardstatus alwaysfirstline '%{= G}[ %{G}%H %{g}][%= %{= w}%?%-Lw%?%{= R}%n*%f %"""Convert this GNU Screen 4 hardstatus .screenrc line into GNU Screen 5 syntax:
Nuno Silva <nunojsilva@invalid.invalid> writes:
Right...it's the *doing* part I'm having an issue with.Google AI: The screen command in Linux is a terminal multiplexer that
allows you to start a terminal session and then completely detach from
it. This leaves your processes running in the background, making it an
invaluable tool for executing long-running tasks over SSH without
worrying about network drops or accidental disconnections.
Ie, similar to tmux. I gather you can customize the status line.
Ask it what is a hard status line, to see if it gets that part right :-) >>>> /set nothinkSet 'nothink' mode.
A **GNU `screen` hardstatus** line is a special configurationWhat is a GNU Screen hardstatus line?
string defined in the `.screenrc` file (or passed via command-line
options) that controls the content displayed on the very last
line of every visible screen window.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:20:25 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |