On Mon, Mar 18, 2024 at 6:26 PM Zachary Santer wrote:
> {
> declare -p assoc
> printf '\x00'
> } >&"${fd}"
> in bash 4.2, which I'm actually pretty happy with.
Rather. No %s there.
Was "Re: nameref and referenced variable scope, setting other attributes"
On Mon, Mar 18, 2024 at 4:20 PM Chet Ramey wrote:
>
> On 3/14/24 8:57 PM, Zachary Santer wrote:
> >
> > While we're kind of on the subject, I find it really odd that the
> > ${var@A} parameter expansion will expand to eithe
On 3/14/24 8:57 PM, Zachary Santer wrote:
On Thu, Mar 14, 2024 at 3:43 PM Chet Ramey wrote:
In fact, before 2020, local -p with no name arguments behaved the same as
local without arguments, which just printed all the local variable names at
the current scope in the form of assignment statemen
On 3/18/24 3:41 PM, Chet Ramey wrote:
It should be mostly there in the changes I pushed today, once I made it
through the above.
I appreciate the work you did. Using the ckd_* macros is the right approach.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars l
On 3/18/24 2:13 PM, nasm--- via Bug reports for the GNU Bourne Again SHell
wrote:
Bash Version: 5.2
Patch Level: 15
Release Status: release
Description:
There is a typo in the bash man page, in Chapter CONDITIONAL EXPRESSION,
second sentence :
"The test abd [ commands determine the
From: fil...@mailo.com
To: bug-bash@gnu.org
Subject: Small typo in bash man-page
Configuration Information [Automatically generated, do not change]:
Machine: aarch64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall
uname output:
On 3/18/24 12:36 PM, Paul Eggert wrote:
On 3/18/24 07:40, Chet Ramey wrote:
Thanks for the patches. They introduce a number of regressions, some due
to the different overflow handling; several not. I urge everyone who
submits non-trivial patches to run the test suite (`make tests') on their
patc
Chet Ramey writes:
> On 3/17/24 12:50 PM, tpeplt wrote:
>> Searching the file bash-master/doc/bashref.texi gives no instance of
>> "syslog" or "syslog_history". An entry for ‘syslog_history’ is provided
>> in the ‘man’ page for ‘bash’:
>> syslog_history
>>If set, command history
On 3/18/24 07:40, Chet Ramey wrote:
Thanks for the patches. They introduce a number of regressions, some due
to the different overflow handling; several not. I urge everyone who
submits non-trivial patches to run the test suite (`make tests') on their
patched versions before sending them in.
I
On Mon, Mar 18, 2024, 15:40 Chet Ramey wrote:
> On 3/13/24 8:57 PM, Paul Eggert wrote:
>
> > Revised patchset attached. The first patch uses the fix you suggested;
> the
> > remaining patches are similar to what I sent earlier, except the last
> one
> > is simplified since it doesn't need to worr
On 3/13/24 8:57 PM, Paul Eggert wrote:
Revised patchset attached. The first patch uses the fix you suggested; the
remaining patches are similar to what I sent earlier, except the last one
is simplified since it doesn't need to worry about inline width and
precision when printf will do the chec
On 3/17/24 12:50 PM, tpeplt wrote:
Bash Maintainers,
The texinfo version of the bash manual is missing a description of
the ‘shopt’ option ‘syslog_history’. This can be confirmed by
downloading bash-master.tar.gz from:
It's an optional feature that is not enabled without special effort. I
On 3/17/24 1:24 AM, Abigail Read wrote:
As of
Reference Documentation for Bash Edition 5.2, for Bash Version 5.2.
September 2022
In 3.1.2.5 Locale-Specific Translation
Quoting from the first paragraph of this section:
If the current locale is C or POSIX, if there are no translations available, o
13 matches
Mail list logo
