Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15277 > unrolled thread
| Started by | L A Walsh <bash@tlinx.org> |
|---|---|
| First post | 2019-07-30 00:46 -0700 |
| Last post | 2019-07-30 00:46 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: ulimit call lists invalid options L A Walsh <bash@tlinx.org> - 2019-07-30 00:46 -0700
| From | L A Walsh <bash@tlinx.org> |
|---|---|
| Date | 2019-07-30 00:46 -0700 |
| Subject | Re: ulimit call lists invalid options |
| Message-ID | <mailman.237.1564472811.1985.bug-bash@gnu.org> |
On 2019/07/29 22:09, Robert Elz wrote:
> Whether bash ought limit its usage output option list to those
> options supported on the system it is running on, or whether it
> is better to list everything it knows about (either my, or your,
> system might have more limits bash knows nothing about) is a
> judgement call - neither answer will be right for everyone.
>
It isn't a judgment call to list only the options it supports on a given
system. I'd think that would be clear. If not at runtime, then
certainly when the bash binary is built, the options for the system
it will run on can be tested so the bash binary is configured for the
system it is running on.
> The modified script (using shell idioms, rather that
> whatever language you were trying to emulate):
>
---
I was not emulating any language, nor was I writing for your
approval. I was going for a minimal script to show the error case
in bash script.
Back to top | Article view | gnu.bash.bug
csiph-web