Re: odd error from bash exec binary on cmd line

On 3/24/18 3:31 PM, L A Walsh wrote: > bash sleep 1 > > I get: > > /usr/bin/sleep: /usr/bin/sleep: cannot execute binary file > > ??? > Isn't it bash that cannot execute the binary file because > it expected a script? Think about what happens when you run a command like that. Bash sees that it

Re: weird bash5 bug with ``for i; do echo; done; echo in''

On 3/24/18 11:24 AM, Clark Wang wrote: > Hi Chet, > > Today I compiled bash5 (using default configuration) from the devel branch > (f602026a0ce - commit bash-20180316 snapshot) on macOS and found it breaks > one of my rc files. After some time of debugging I have the following > minimal example to

Re: bash long prompt, color going past the end of prompt after reaching bottom of terminal

On 3/23/18 12:47 PM, Musse Abdullahi wrote: > Virta, > > your workaround solves the first issue but creates another one. > > Here is the script with your workaround > > |calculate_prompt1(){host="my-linux"git_branch="a very very very very very > very very very very very very very very very long

Re: [PATCH] fix a bug that bind -x '"\C-@": unix-command' does not work

On 3/20/18 12:35 PM, Koichi Murase wrote: > Bash Version: 4.4 > Patch Level: 12 > Release Status: release > > > Description: > > In bash-4.3.43, bash-4.4.12, and the latest commit of the devel > branch, `bind -x' does not work for key sequences containing `\C-@'. Thanks for the report and pa

Re: bash handles terminate signals incorrectly, when it is run as the init process in a pid namespace

On 3/23/18 4:34 AM, Andrei Vagin wrote: > On Thu, Mar 22, 2018 at 6:25 PM, Chet Ramey wrote: >> On 3/22/18 3:38 PM, Andrei Vagin wrote: >> >>> I am thinking how to fix this issue properly. Here are a few points: >>> * bash should know that signals are ignored if a process is the init >>> process i