Hi Ian,
Ian Jackson wrote:
> > I also tried to modify your patch to at least get a non-zero exit code
> > or a visible error message in your case, but failed so far for both.
>
> I will also look at this, but probably not until tonight. Will that
> be soon enough for you ?
I've uploaded 4.9.0-1 last night with urgency=low to catch potential
issues to report upstream before 4.9.1 is out. But I'm open to do
another upload, if we find a patch that clearly alarms the user about
this issue.
Just to make it clear, the following is the test case as I understood
and tried it:
$ screen screen ../t.sh {0..999}
[screen is terminating]
$ echo $?
0
$
It should show an error message in addition or instead of "[screen is
terminating]" and exit with a non-zero exit code. I though would
already accept a patch if even one of the conditions is already better
than now.
Working inside a Screen session with "Ctrl-A : screen" is IMHO less
important as the chance for typing more than 62 parameters manually
into a screen session at the colon prompt seems rather seldom. And it
actually also works — at least if the window is wide enough, see my
new upstream bug report at https://savannah.gnu.org/bugs/?61980
Feel free to work in the debian-bug-1000138 branch at
https://salsa.debian.org/debian/screen/-/tree/debian-bug-1000138
It is currently at the master branch plus your original patch with
"crash" replaced by "die". ("panic" instead of "crash" would be fine
as well.)
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
