>From debian:
https://lists.debian.org/debian-cross/2023/11/msg0.html
Hello,
While cross-building hurd-amd64 from linux, I got a subtle issue with
bash, that was leading to perl FTBFS very oddly.
The issue essentially was in bash/builtins/Makefile.in:
pipesize.h: psize.aux
$(SH
On Mon, 25 Nov 2024 at 01:08, Andreas Kähäri wrote:
> I don't agree that the special parameters should be written as $! etc.
> since those are their _values_ when used in the shell (exactness is a
> virtue in a manual).
>
In a *printed* manual I would agree with you, but in a man page where the
On Sun, Nov 24, 2024 at 02:58:45PM -0500, Lawrence Velázquez wrote:
> On Sun, Nov 24, 2024, at 10:08 AM, Andreas Kähäri wrote:
> > On Sun, Nov 24, 2024 at 09:31:42AM -0500, Greg Wooledge wrote:
> >> Similar cases exist elsewhere within the man page. For example, if you
> >> search for $! or $$ you
On Sun, Nov 24, 2024, at 10:08 AM, Andreas Kähäri wrote:
> On Sun, Nov 24, 2024 at 09:31:42AM -0500, Greg Wooledge wrote:
>> Similar cases exist elsewhere within the man page. For example, if you
>> search for $! or $$ you will not find the section that documents them.
>> You would have to know th
On Sunday, November 24, 2024, Martin D Kealey
wrote:
>
> This REALLY needs to be driven home both in the explanation and with
> examples, preferably with at least one that illustrates using more than one
> character class inside one match group.
>
In another document, not the manual.
--
Oğuz
On Sun, Nov 24, 2024 at 22:51:43 +1000, Martin D Kealey wrote:
> When one *doesn't *already know how it works, “using the syntax *[:class:]*”
> could just as easily mean using *:class:* inside *[…]*.
Yeah, good luck with that. I predict that if you offer a patch to
make this clearer, there will b
I don't see anyting wrong with the patch, but...
+bug reports may be [...] posted to the Usenet newsgroup
> .BR gnu.bash.bug .
>
Ummm?
Does Chet still read Usenet?
Does anyone else?
-Martin
PS: Sometimes I miss the good old days when Usenet was the social glue that
held a small worldwide com
On Sun, Nov 24, 2024 at 02:29:01AM +, marcel.plch via Bug reports for the
GNU Bourne Again SHell wrote:
> On Sunday, November 24th, 2024 at 3:05 AM, Lawrence Velázquez
> wrote:
>
> > On Sat, Nov 23, 2024, at 7:11 PM, marcel.plch via Bug reports for the GNU
> > Bourne Again SHell wrote:
> >
On Sun, Nov 24, 2024 at 09:31:42AM -0500, Greg Wooledge wrote:
> On Sun, Nov 24, 2024 at 22:51:43 +1000, Martin D Kealey wrote:
> > When one *doesn't *already know how it works, “using the syntax *[:class:]*”
> > could just as easily mean using *:class:* inside *[…]*.
>
> Yeah, good luck with that
On Sun, 24 Nov 2024 at 18:05, Andreas Kähäri wrote:
> I think the manual is quite clear:
>
> Within [ and ], character classes can be specified
> using the syntax [:class:], where class is one of the
> following classes defined in the POSIX standard:
> alnum alpha
On Sun, Nov 24, 2024 at 7:52 AM Martin D Kealey wrote:
>
> When one already knows how it works, that's obvious, and it's hard to see
> how it could mean anything else.
>
> When one *doesn't *already know how it works, “using the syntax *[:class:]*”
> could just as easily mean using *:class:* insid
On Sun, Nov 24, 2024 at 10:51:43PM +1000, Martin D Kealey wrote:
> On Sun, 24 Nov 2024 at 18:05, Andreas Kähäri wrote:
>
> > I think the manual is quite clear:
> >
> > Within [ and ], character classes can be specified
> > using the syntax [:class:], where class is one of the
> >
12 matches
Mail list logo
