Re: Wrong command option in the manual examples

2019-09-23 Thread Robert Elz
Date:Mon, 23 Sep 2019 14:12:27 -0400 From:Chet Ramey Message-ID: <49989bf9-7c12-2670-de3f-20feead50...@case.edu> | It's in SVR2 (1984?), at least, Thanks. | The SVR2 page implies that it was added to support cpio. Yes .. the function of the option is fine -

Re: Wrong command option in the manual examples

2019-09-23 Thread Chet Ramey
On 9/23/19 1:24 PM, Robert Elz wrote: > Date:Mon, 23 Sep 2019 10:59:43 -0400 > From:Greg Wooledge > Message-ID: <20190923145943.gx28...@eeg.ccf.org> > > | But... there literally *is* a real standard for this. > > Hmm, yes, you're right. That suggests that -depth

Re: Documentation Bug Concerning Regular Expressions?

2019-09-23 Thread Ilkka Virta
On 23.9. 19:56, Hults, Josh wrote: Hello Bash Maintainers, In the currently posted version of the Bash documentation, there is a section regarding Conditional Constructs (3.2.4.2, https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Conditional-Constructs). Within that section

nocaseglob and RE matching

2019-09-23 Thread Grisha Levit
Currently nocaseglob and nocasematch both control case insensitivity of RE matching (in lib/sh/smatch.c): if (glob_ignore_case || match_ignore_case) rflags |= REG_ICASE; However, the documentation suggests that only nocasematch should have this effect. I'm guessing this behavior was in

Documentation Bug Concerning Regular Expressions?

2019-09-23 Thread Hults, Josh
Hello Bash Maintainers, In the currently posted version of the Bash documentation, there is a section regarding Conditional Constructs (3.2.4.2, https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Conditional-Constructs). Within that section is a portion discussing the [[ ... ]]

Re: Wrong command option in the manual examples

2019-09-23 Thread Robert Elz
Date:Mon, 23 Sep 2019 10:59:43 -0400 From:Greg Wooledge Message-ID: <20190923145943.gx28...@eeg.ccf.org> | But... there literally *is* a real standard for this. Hmm, yes, you're right. That suggests that -depth must be a System-V invention (POSIX wouldn't have

Re: Regular Expression matching operation =~

2019-09-23 Thread Allodoxaphobia
On Mon, 23 Sep 2019 09:21:44 -0400, Chet Ramey wrote: > On 9/22/19 5:44 PM, Allodoxaphobia wrote: > >> In moving a bash ver. 4.3.48 (Ubuntu) program to a bash ver. 5.0.11 >> (FreeBSD) environment I encountered either a bug, a quirk, or >> an undocumented feature. > > It's not exactly undocumented,

Re: Wrong command option in the manual examples

2019-09-23 Thread Robert Elz
Date:Mon, 23 Sep 2019 16:36:59 +0200 From:Andreas Schwab Message-ID: | According to https://www.freebsd.org/cgi/man.cgi, find -d already | appeared in 4.3BSD, and -depth is much newer. I can believe that, I did not research the history, just what is in the

Re: Wrong command option in the manual examples

2019-09-23 Thread Greg Wooledge
On Mon, Sep 23, 2019 at 09:02:47PM +0700, Robert Elz wrote: > There is no real standard for this - NetBSD has deprecated the -depth > operator (which never really was one) and replaced it by a -d option > which makes much more sense (-depth never really was the right way to > do it). -depth (the

Re: Wrong command option in the manual examples

2019-09-23 Thread Andreas Schwab
On Sep 23 2019, Robert Elz wrote: > Date:Mon, 23 Sep 2019 12:29:18 +0300 > From:Ilkka Virta > Message-ID: <59cf49b0-1292-b752-4fe8-8928fd558...@iki.fi> > > | (as well the standard '-depth', somewhat confusingly) > > There is no real standard for this - NetBSD has

Re: Wrong command option in the manual examples

2019-09-23 Thread Robert Elz
Date:Mon, 23 Sep 2019 12:29:18 +0300 From:Ilkka Virta Message-ID: <59cf49b0-1292-b752-4fe8-8928fd558...@iki.fi> | (as well the standard '-depth', somewhat confusingly) There is no real standard for this - NetBSD has deprecated the -depth operator (which never

Re: [PATCH] Add active mark, face support; activate mark on paste

2019-09-23 Thread Chet Ramey
On 9/23/19 7:32 AM, Daniel Colascione wrote: > On Wed, Jan 9, 2019 at 12:37 PM Chet Ramey wrote: >> >> On 1/9/19 2:39 PM, Daniel Colascione wrote: >>> Any chance we can revive this patch now that Bash 5 is out? (The patch >>> itself, of course, would need to be rebased.) >> >> Yes, I plan to. >

Re: Wrong command option in the manual examples

2019-09-23 Thread Chet Ramey
On 9/23/19 5:29 AM, Ilkka Virta wrote: > On 22.9. 21:15, Chet Ramey wrote: >> On 9/20/19 10:24 PM, hk wrote: >> >>> Bash Version: 5.0 >>> Patch Level: 0 >>> Release Status: release >>> >>> Description: >>> On the section 3.2.6(GNU Parallel, page 16 in the pdf) of Bash >>> Reference

Re: Regular Expression matching operation =~

2019-09-23 Thread Chet Ramey
On 9/22/19 5:44 PM, Allodoxaphobia wrote: > In moving a bash ver. 4.3.48 (Ubuntu) program to a bash ver. 5.0.11 > (FreeBSD) environment I encountered either a bug, a quirk, or > an undocumented feature. It's not exactly undocumented, more undefined. You can't count on the NUL character or the

Re: [PATCH] Add active mark, face support; activate mark on paste

2019-09-23 Thread Daniel Colascione
On Wed, Jan 9, 2019 at 12:37 PM Chet Ramey wrote: > > On 1/9/19 2:39 PM, Daniel Colascione wrote: > > Any chance we can revive this patch now that Bash 5 is out? (The patch > > itself, of course, would need to be rebased.) > > Yes, I plan to. Have you had a chance to look at the patch?

Re: Wrong command option in the manual examples

2019-09-23 Thread Ilkka Virta
On 22.9. 21:15, Chet Ramey wrote: On 9/20/19 10:24 PM, hk wrote: Bash Version: 5.0 Patch Level: 0 Release Status: release Description: On the section 3.2.6(GNU Parallel, page 16 in the pdf) of Bash Reference Manual. The manual uses `find' command to illustrate possible use cases of