Re: Officially document that we allow other characters in function names

On Tue, Jun 28, 2016 at 5:04 AM, Chet Ramey wrote: > On 6/27/16 1:56 PM, konsolebox wrote: > >>> Chet is one of these people ;) >>> https://lists.gnu.org/archive/html/bug-bash/2011-04/msg00040.html >> >> Well it wasn't a mistake for me. At least I find the characters '.' >> and '?' (and maybe '!

Re: Officially document that we allow other characters in function names

On Tue, Jun 28, 2016 at 5:02 AM, Chet Ramey wrote: > On 6/27/16 1:15 PM, Pierre Gaston wrote: >> >> >> On Mon, Jun 27, 2016 at 7:17 PM, konsolebox > > wrote: >> >> On Mon, Jun 27, 2016 at 10:41 PM, Chet Ramey > > wrote: >> > On 6

Re: Officially document that we allow other characters in function names

On 6/27/16 1:15 PM, Pierre Gaston wrote: > > > On Mon, Jun 27, 2016 at 7:17 PM, konsolebox > wrote: > > On Mon, Jun 27, 2016 at 10:41 PM, Chet Ramey > wrote: > > On 6/27/16 3:11 AM, konsolebox wrote: > >> Hi, I think it's

Re: Officially document that we allow other characters in function names

On 6/27/16 1:56 PM, konsolebox wrote: >> Chet is one of these people ;) >> https://lists.gnu.org/archive/html/bug-bash/2011-04/msg00040.html > > Well it wasn't a mistake for me. At least I find the characters '.' > and '?' (and maybe '!' as well) helpful. You just have to be careful that `?' d

Re: Officially document that we allow other characters in function names

On Tue, Jun 28, 2016 at 1:31 AM, Pierre Gaston wrote: > > > On Mon, Jun 27, 2016 at 8:15 PM, Pierre Gaston > wrote: >> >> >> >> On Mon, Jun 27, 2016 at 7:17 PM, konsolebox wrote: >>> >>> On Mon, Jun 27, 2016 at 10:41 PM, Chet Ramey wrote: >>> > On 6/27/16 3:11 AM, konsolebox wrote: >>> >> Hi, I

Re: Officially document that we allow other characters in function names

On Tue, Jun 28, 2016 at 1:15 AM, Pierre Gaston wrote: > > > On Mon, Jun 27, 2016 at 7:17 PM, konsolebox wrote: >> >> On Mon, Jun 27, 2016 at 10:41 PM, Chet Ramey wrote: >> > On 6/27/16 3:11 AM, konsolebox wrote: >> >> Hi, I think it's time that we officially specify in the manual of Bash >> >> t

Re: Bash 4.3.11(1) crashes after running exec

On Mon, Jun 27, 2016 at 08:25:06PM +0300, #pragma wrote: > Thank you. You are right, it was just confusing to see on the screen of > Konsole terminal that "bash program was crashed". So bash not doing > fork() before exec? It looks like a father process crashes. Crash is > always undesired and unex

Re: Officially document that we allow other characters in function names

On Mon, Jun 27, 2016 at 8:15 PM, Pierre Gaston wrote: > > > On Mon, Jun 27, 2016 at 7:17 PM, konsolebox wrote: > >> On Mon, Jun 27, 2016 at 10:41 PM, Chet Ramey wrote: >> > On 6/27/16 3:11 AM, konsolebox wrote: >> >> Hi, I think it's time that we officially specify in the manual of Bash >> >> t

Re: Bash 4.3.11(1) crashes after running exec

> Again, what do you expect to happen? You replace the bash process -- it > goes away. As soon as the man process terminates, your session ends. This > is what `exec' does. > Thank you. You are right, it was just confusing to see on the screen of Konsole terminal that "bash program was crash

Re: Officially document that we allow other characters in function names

On Mon, Jun 27, 2016 at 7:17 PM, konsolebox wrote: > On Mon, Jun 27, 2016 at 10:41 PM, Chet Ramey wrote: > > On 6/27/16 3:11 AM, konsolebox wrote: > >> Hi, I think it's time that we officially specify in the manual of Bash > >> that we allow other characters besides [[:alnum:]_] when declaring >

Re: Bash 4.3.11(1) crashes after running exec

On 6/27/16 12:52 PM, #pragma wrote: > Thank you for the answer. I would agree with you, but there is something > more. > If I change command from the first step to this: > > user@host:~$ exec man man man > > and leave other steps as were before, then bash crashes as well. Also on > tty logins. A

Re: Bash 4.3.11(1) crashes after running exec

Thank you for the answer. I would agree with you, but there is something more. If I change command from the first step to this: user@host:~$ exec man man man and leave other steps as were before, then bash crashes as well. Also on tty logins. Regards, Michael On 06/27/2016 05:40 PM, Chet Ramey

Re: Officially document that we allow other characters in function names

On Mon, Jun 27, 2016 at 10:41 PM, Chet Ramey wrote: > On 6/27/16 3:11 AM, konsolebox wrote: >> Hi, I think it's time that we officially specify in the manual of Bash >> that we allow other characters besides [[:alnum:]_] when declaring >> function names in non-POSIX mode. > > Is there some new rea

Re: Officially document that we allow other characters in function names

On 6/27/16 3:11 AM, konsolebox wrote: > Hi, I think it's time that we officially specify in the manual of Bash > that we allow other characters besides [[:alnum:]_] when declaring > function names in non-POSIX mode. Is there some new reason to do this now? -- ``The lyf so short, the craft so lon

Re: Bash 4.3.11(1) crashes after running exec

On 6/26/16 4:55 PM, #pragma wrote: > Hello! > > OS: Kubuntu 14.04 > Bash version: 4.3.11(1)-release (i686-pc-linux-gnu) > > How to reproduce a bug: > > (1) > user@host:~$ exec man !!! What do you expect to happen? You're replacing the bash process with man against a totally bizarre set

Bash 4.3.11(1) crashes after running exec

Hello! OS: Kubuntu 14.04 Bash version: 4.3.11(1)-release (i686-pc-linux-gnu) How to reproduce a bug: (1) user@host:~$ exec man !!! (2) Then, on man execution, press q (3) On this stage, if bash didn't exited and there is a line on the screen: --Man-- next: man(1) [ view (return) | ski

Officially document that we allow other characters in function names

Hi, I think it's time that we officially specify in the manual of Bash that we allow other characters besides [[:alnum:]_] when declaring function names in non-POSIX mode. In the Bash manual, the only thing we specify about the definition of shell functions under POSIX mode is "When in posix mode,