Re: [PATCH 3/4] check-non-portable-shell: improve `VAR=val shell-func` detection

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 22, 2024, 18:10 UTC
Message-ID: <xmqq34o1cn6b.fsf@gitster.g>
In-Reply-To: <CAO_smVg8+WCG0dWZNPVbDM4gBJLLHrg96nOCzje6B3hUGneDGg@mail.gmail.com>

Kyle Lippincott <spectral@google.com> writes:

> Is there an example of a shell on Linux that has this behavior that I
> can observe, and/or reproduction steps?

Every once in a while this comes up and we fix, e.g.

https://lore.kernel.org/git/528CE716.8060307@ramsay1.demon.co.uk/ https://lore.kernel.org/git/c6efda03848abc00cf8bf8d84fc34ef0d652b64c.1264151435.git.mhagger@alum.mit.edu/ https://lore.kernel.org/git/Koa4iojOlOQ_YENPwWXKt7G8Aa1x6UaBnFFtliKdZmpcrrqOBhY7NQ@cipher.nrlssc.navy.mil/ https://lore.kernel.org/git/20180713055205.32351-2-sunshine@sunshineco.com/ https://lore.kernel.org/git/574E27A4.6040804@ramsayjones.plus.com/

which is from a query

    https://lore.kernel.org/git/?q=one-shot+export+shell+function

but unfortunately we do not document which exact shell the observed breakage happened with.

The closest article I found that is suitable as a discussion reignitor talks about what POSIX requires, which may be more relevant:

  https://lore.kernel.org/git/4B5027B8.2090507@viscovery.net/