Re: Bash 5 increase in RAM from loop with many interations that append to file

2020-10-27 Thread Scott Kostyshak
On Tue, Oct 27, 2020 at 09:40:53AM -0400, Chet Ramey wrote: > On 10/27/20 12:11 AM, Scott Kostyshak wrote: > > The following example uses more peak RAM on new bash versions than old > > versions: > > > > for i in {1..100}; do > > echo "${i}" >> example.txt > > done > > > > By measuring pea

Re: Bash 5 increase in RAM from loop with many interations that append to file

2020-10-27 Thread Scott Kostyshak
On Tue, Oct 27, 2020 at 08:54:37PM +0900, Koichi Murase wrote: > > I tried to bisect but I'm not sure the result is useful. I got the > > following: > > > > d233b485e83c3a784b803fb894280773f16f2deb is the first bad commit > > commit d233b485e83c3a784b803fb894280773f16f2deb > > Author: Chet R

Re: Behavior change

2020-10-27 Thread Chet Ramey
On 10/27/20 10:10 AM, Gregory Heytings wrote: > >>> Okay.  I just set "set enable-bracketed-paste off" in my /etc/inputrc. >>> Perhaps this change should be documented in CHANGES, and in the man page >>> (where enable-bracketed-paste is said to have the default value Off). >> >> The manual page in

Re: Behavior change

2020-10-27 Thread Gregory Heytings via Bug reports for the GNU Bourne Again SHell
Okay.  I just set "set enable-bracketed-paste off" in my /etc/inputrc. Perhaps this change should be documented in CHANGES, and in the man page (where enable-bracketed-paste is said to have the default value Off). The manual page in the released version will reflect the default setting of

Re: Behavior change

2020-10-27 Thread Chet Ramey
On 10/27/20 9:55 AM, Gregory Heytings wrote: > > Okay.  I just set "set enable-bracketed-paste off" in my /etc/inputrc. > Perhaps this change should be documented in CHANGES, and in the man page > (where enable-bracketed-paste is said to have the default value Off). The manual page in the releas

Re: Bash 5 increase in RAM from loop with many interations that append to file

2020-10-27 Thread Chet Ramey
On 10/27/20 12:11 AM, Scott Kostyshak wrote: > The following example uses more peak RAM on new bash versions than old > versions: > > for i in {1..100}; do > echo "${i}" >> example.txt > done > > By measuring peak memory usage with time (/usr/bin/time -f "%E %P %M"), > I get that newer ver

Re: Behavior change

2020-10-27 Thread Gregory Heytings via Bug reports for the GNU Bourne Again SHell
Hi Chet, Thanks for your reply! I just installed Bash 5.1 rc1.  I have IGNOREEOF set, and in 5.0 (and earlier version) when pressing C-d one sees: $ Use "logout" to leave the shell. With 5.1 rc1 there is a newline between the prompt and the message: $ Use "logout" to leave the shell. Is

Re: Behavior change

2020-10-27 Thread Chet Ramey
On 10/26/20 5:58 PM, Gregory Heytings via Bug reports for the GNU Bourne Again SHell wrote: > > Hi, > > I just installed Bash 5.1 rc1.  I have IGNOREEOF set, and in 5.0 (and > earlier version) when pressing C-d one sees: > > $ Use "logout" to leave the shell. > > With 5.1 rc1 there is a newline

Re: Bash 5 increase in RAM from loop with many interations that append to file

2020-10-27 Thread Koichi Murase
> I tried to bisect but I'm not sure the result is useful. I got the following: > > d233b485e83c3a784b803fb894280773f16f2deb is the first bad commit > commit d233b485e83c3a784b803fb894280773f16f2deb > Author: Chet Ramey > Date: Mon Jan 7 09:27:52 2019 -0500 > > bash-5.0 distributio