This can be reproduced in noble. I don't particularly think this is a
bug either but rather an undocumented design decision.
Imre, I think the best action here is to ask upstream to change the
value higher, or to document the max character length better.
--
You received this bug notification
seems like screen -S "$magic" -Logfile "${screen_logfile}" is not a
drop-in replacement for screen -S "$magic" -X colon "logfile
${screen_logfile}^M"
in my use case, at least for the time being, logfile is expected to be
set after the session is already created
also, my terminal windows are 166
Hi Imre,
This seems to be truncated due to the width of your terminal window,
since "colon" is used as a command through the window and it does not
span new lines when a command is longer than the window witdh.
However, there is a -L option you could pass to screen to set a new
logfile name
as a workaround you can make a softlink to your logfile. the length of
the filename of the actual logfile doesn't matter, the length of the
filename of the softlink should be below 70 chars. And make your screen
to log into the softlink
--
You received this bug notification because you are a
