Re: [PATCH] doc: missing parameter expansion operators in bash(1)
From:
Connor Wilkins
Subject:
Re: [PATCH] doc: missing parameter expansion operators in bash(1)
Date:
Wed, 27 Aug 2025 15:22:10 +0000
On 8/27/25 10:36 AM, Chet Ramey wrote:
> On 8/27/25 10:29 AM, Zachary Santer wrote:
>> On Wed, Aug 27, 2025 at 10:19 AM Chet Ramey <chet.ramey@case.edu> wrote:
>>>
>>> On 8/26/25 6:40 PM, Zachary Santer wrote:
>>>>
>>>> Not that I've ever had a use
>>>> for a case-toggling word expansion, but there's no alternative that's
>>>> documented, aside from calling an external command.
>>>
>>> You've never found a use for one, but bash should provide one because
>>> there's no documented alternative?
>>
>> Bash already provides one. You're just leaving it undocumented so
>> you're more free to get rid of it in the future?
> I'm leaving it undocumented to discourage its use, yes. One thing I've
> discovered is that you can never remove a feature (e.g. $[expr]).
> Is it useful enough to add a parameter transformation for it? What should
> bash use for the operator?
>> Did it originate in
>> another shell?
> No.
I'm of the opinion that if there is a supported feature with no plans for
deprecation
or removal, it should be documented. Even if it's not widely used, it's still
supported
with (as you said) no plans for removal.