On Wed, 2021-08-11 at 20:36 -0400, Greg Wooledge wrote:
> On Wed, Aug 11, 2021 at 08:00:12PM -0400, Franklin, Jason wrote:
> > This doesn't work unless it was recently fixed. A variation does...
> >
> > bash-5.0$ echo $BASH_VERSION
> > 5.0.17(1)-release
> > bash-5.0$ GROUPS=FOO bash -c 'echo $GRO
On Wed, Aug 11, 2021 at 08:00:12PM -0400, Franklin, Jason wrote:
> This doesn't work unless it was recently fixed. A variation does...
>
> bash-5.0$ echo $BASH_VERSION
> 5.0.17(1)-release
> bash-5.0$ GROUPS=FOO bash -c 'echo $GROUPS'
> 1000
> bash-5.0$ GROUPS=FOO bash --posix -c 'echo $GROUPS'
>
Chet:
My apologies in advance for not responding in thread. The bug-bash
archive interface doesn't expose the "Message-ID" header anywhere I can
find, and I am not a subscriber. I suppose I should become one. :)
> I believe I'd rather have variables behave as they're documented. It's more
> pr
Le 10/08/2021 à 17:22, Chet Ramey a écrit :
This is the current description:
noexpand_translation
If set, bash encloses the translated results of $"..."
quoting in single quotes instead of double quotes. If
the string is not translate
On Wed, 11 Aug 2021, Chet Ramey wrote:
On 8/10/21 5:08 PM, Chris F.A. Johnson wrote:
It would be nice if there were an option to allow * to expand sorted
by timestamp rather than aphabetically.
When you say `timestamp' I assume you mean by last modification time.
Yes, that's what I meant.
On 8/11/21 2:06 PM, Robert Elz wrote:
Date:Wed, 11 Aug 2021 10:16:42 -0400
From:Chet Ramey
Message-ID: <26e01365-d7f0-448d-dc4d-83f244bd0...@case.edu>
| As long as POSIX doesn't define a variable to have some special meaning, it
| doesn't have anything to s
Date:Wed, 11 Aug 2021 10:16:42 -0400
From:Chet Ramey
Message-ID: <26e01365-d7f0-448d-dc4d-83f244bd0...@case.edu>
| As long as POSIX doesn't define a variable to have some special meaning, it
| doesn't have anything to say about how a shell chooses to use it. It's
On Wed, Aug 11, 2021 at 10:43:12AM -0400, Chet Ramey wrote:
> On 8/10/21 5:08 PM, Chris F.A. Johnson wrote:
> >
> > It would be nice if there were an option to allow * to expand sorted
> > by timestamp rather than aphabetically.
>
> When you say `timestamp' I assume you mean by last modification
On 8/10/21 5:08 PM, Chris F.A. Johnson wrote:
It would be nice if there were an option to allow * to expand sorted
by timestamp rather than aphabetically.
When you say `timestamp' I assume you mean by last modification time.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
On 8/10/21 2:56 PM, Mike Jonkmans wrote:
noexpand_translation
If set, bash encloses the translated results of $"..."
quoting in single quotes instead of double quotes. If
the string is not translated, this has no effect.
It will be in
On 8/10/21 8:56 PM, Franklin, Jason wrote:
What surprised me was that Bash-specific "magic" variables did not lose
their "magic" qualities when Bash was invoked in a POSIX-compliant mode
of execution.
That's not what bash posix mode is for. POSIX does not prohibit extensions.
--
``The lyf
On 8/10/21 12:39 PM, Robert Elz wrote:
| In this case, you are using features outside what POSIX specifies.
Using a variable name that's outside what POSIX specifies is hardly
using a feature that's outside POSIX - if it were then there would be
no safe non-trivial scripts, since any variabl
On Aug 11 2021, Štěpán Němec wrote:
> Quoting POSIX.1-2017 on environment variables [1]:
Note that GROUPS is not an environment variable in bash, it is not
exported.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And
On Tue, 10 Aug 2021 23:39:47 +0700
Robert Elz wrote:
> Date:Tue, 10 Aug 2021 10:22:29 -0400
> From:Chet Ramey
> Message-ID: <731876fc-39c0-4388-0c9e-bf560921b...@case.edu>
>
> | In this case, you are using features outside what POSIX specifies.
>
> Using a variable
14 matches
Mail list logo
