Re: Command substitution with null bytes generates warning

2016-10-05 Thread Eric Pruitt
On Wed, Oct 05, 2016 at 09:20:58AM -0400, Chet Ramey wrote: > Try the attached patch, which reduces the number of warnings to 1 per call > to command substitution. I don't agree with this approach -- I think you should be able to turn off the warning completely, so I am not interested in testing t

Re: Command substitution with null bytes generates warning

2016-10-05 Thread Chet Ramey
On 9/16/16 1:51 AM, Eric Pruitt wrote: > Bash Version: 4.4 > Patch Level: 0 > Release Status: release > > Description: > I have a script that execute `if [[ "$(<"/proc/$1/cmdline")" = tmux* > ]];`. > All /proc/*/cmdline include null bytes, and as of Bash 4.4, this > results in >

Re: bash history with mixed timestamps slow and broken

2016-10-05 Thread Chet Ramey
On 9/25/16 6:39 PM, Chet Ramey wrote: > On 9/24/16 2:17 PM, Hubert Schmid wrote: >> Bash Version: 4.4 >> Patch Level: 0 >> Release Status: release >> >> Description: >> If the history file (`.bash_history`) starts with a timestamp >> (`HIST_TIMESTAMP_START`), and contains lines that have

Re: "HISTSIZE=999999999" cause bash failure after lastest upgrade

2016-10-05 Thread Chet Ramey
On 9/25/16 6:59 PM, Chet Ramey wrote: > On 9/25/16 3:51 PM, Sean Zha wrote: > >> Bash Version: 4.4 >> Patch Level: 0 >> Release Status: release >> >> Description: >> I use a huge value for HISTSIZE (=9) to enable infinite >> history items. The actural size of ~/.bash_history is o