Re: sh(1): POSIX "Command Search and Execution"

Date:Fri, 20 Sep 2024 18:53:11 +0200 From: Message-ID: | For some reason[*], I looked at sh(1) "Command Search and Execution" | in POSIX (issue 7 2018 and then issue 8 2024). Over the past many years this has been one of the most debated parts of the specificatio

Re: etiquette for new failing test cases, followed by fix

Am 20.09.2024 um 14:44 schrieb Greg Troxel: > Roland Illig writes: > >> The first commit demonstrates the buggy state by having a test that >> technically succeeds but has lots of FIXME comments in all the places >> that are wrong, already stating what is expected after the bugfix. >> >> The secon

sh(1): POSIX "Command Search and Execution"

For some reason[*], I looked at sh(1) "Command Search and Execution" in POSIX (issue 7 2018 and then issue 8 2024). Starting with the 7th issue (2018), and concerning a command without any slash, the behavior is: ---8<---i7 2018 a) If the command name matches the name of a special built-in util

Re: etiquette for new failing test cases, followed by fix

Roland Illig writes: > The first commit demonstrates the buggy state by having a test that > technically succeeds but has lots of FIXME comments in all the places > that are wrong, already stating what is expected after the bugfix. > > The second commit fixes one of the bugs and updates the tests