Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall
uname output: Linux debtest 6.0.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian
6.0.10-2 (2022-12-01)
I'm far from having the skills of the people here. However, I found the
problem interesting. I think I've come up with a reasonable solution
(you tell me). Although it's not as short as Kerin Millar's, I think it
offers some improvements. I hope there are no particular weaknesses.
If it's of any u
On 28/06/2023 00:40, Kerin Millar wrote:
On Tue, 27 Jun 2023 21:52:53 +0200
of1 wrote:
On 27/06/2023 21:05, Kerin Millar wrote:
It doesn't work at all for >=5.2. The reason for this is interesting and I may
make a separate post about it.
Prior to 5.2, it can easily be tricked into printing
On 28/06/2023 12:42, Fabien Orjollet wrote:
But by adding set -p to the subshell:
Well, works as well by adding :
so I'm not sure at all about set -p
time for i in {1..100}; do
#declare-P "$(set -p; declare -p)"
declare-P "$(:; declare -p)"
done
1>4648 2
On 28/06/2023 14:45, Kerin Millar wrote:
On Wed, 28 Jun 2023 12:42:16 +0200
Fabien Orjollet wrote:
On 28/06/2023 00:40, Kerin Millar wrote:
On Tue, 27 Jun 2023 21:52:53 +0200
of1 wrote:
On 27/06/2023 21:05, Kerin Millar wrote:
It doesn't work at all for >=5.2. The reason for
KS.
Ok, that looks good! I should have found it...
Thanks a lot for the pointer, have a nice day,
--
Fabien
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
