Dear Tom,
In message 20210706153327.GS9516@bill-the-cat you wrote:
Mature? And still without consequent error checking? And done, i. e. this will never be fixed?
Intentional design by upstream, and then for the actual problem part (error checking, test suite), Sean is saying he'll fix it, and has started on it.
Seriously - any piece of software that omits error checking intentionally be design should be indented six feet downward and covered with dirt. We should not even consider looking at it.
OK, snark aside, I'm very serious here, any "we'll just import ..." needs to have a plan to keep it up to date, or be easy enough to do such that I can set a monthly reminder to check for and do the update. Every area where we don't do this is a set of problems waiting to get worse, as we can see with the hush shell right now as it's one of the oldest things we stopped syncing with.
Which exact _new_ problems do we see with hush right now? I can only see old ones, that have been known (and worked around) for nearly two decades.
The limitations and bugs have all been there since the beginning - the limitations actually being intentional due to the typical resource situation at that time.
But I really think we want a shell environment that is not actively adding new features is a good thing, for the default. Just how much stuff should we be doing or need to be doing before we hand things over to the OS?
You are shooting yourself in the knee here.
If you think out CLI should not be adding new features, then we should just stick with our ancient hush and neither update it nor replace it with something else that adds not only new features, but breaks backward compatibility, hard.
Best regards,
Wolfgang Denk