From: Denys Vlasenko <dvlasenk@redhat.com>
To: Harald van Dijk <harald@gigawatt.nl>, dash@vger.kernel.org
Subject: Re: Are there users of ash's "pathopts"? Do other shells have such a thing?
Date: Sat, 1 Apr 2023 22:49:29 +0200 [thread overview]
Message-ID: <e57e26c4-a37f-37e8-90bf-6f19295eab59@redhat.com> (raw)
In-Reply-To: <e69d7554-6047-f527-9489-0d8e872643ae@gigawatt.nl>
On 4/1/23 21:13, Harald van Dijk wrote:
>> I assume it's rarely (never?) used in the wild.
>> It interferes with valid directories with percents in names.
>> It's non-standard, and not a typical feature of other Bourne-like shells
>> (maybe we (ash family) are the only ones?)
>> Code complication to support it is a chore.
>
> It is not clear to me whether you mean "non-standard" as "conflicts with the standard", or "not required by the standard".
"not required".
More importantly, no one else among shells seems to have such extension.
This means it's probably not terribly useful.
There is value in *not* having extensions "just because we can".
Extensions fragment user base.
IOW: extensions make sense when they are *useful*.
Shells already have way too much of featuritis.
Just now, I learned that CDPATH is a thing... oh god.
Yet another danger of subtle bugs in scripts when one
of their innocuous "mkdir subdir; cd subdir" suddenly
cd's somewhere else...
..and this "feature" seems to be in bash too,
and who knows where else.
next prev parent reply other threads:[~2023-04-01 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 18:46 Are there users of ash's "pathopts"? Do other shells have such a thing? Denys Vlasenko
2023-04-01 19:13 ` Harald van Dijk
2023-04-01 20:49 ` Denys Vlasenko [this message]
2023-04-01 21:35 ` Lawrence Velázquez
2023-04-02 17:25 ` Sven Mascheck
2023-04-03 9:35 ` Denys Vlasenko
2023-04-03 11:35 ` Harald van Dijk
2023-04-03 11:54 ` Denys Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e57e26c4-a37f-37e8-90bf-6f19295eab59@redhat.com \
--to=dvlasenk@redhat.com \
--cc=dash@vger.kernel.org \
--cc=harald@gigawatt.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox