From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bash-4.0-r1 for ~arch
Date: Tue, 3 Mar 2009 15:04:26 -0500 [thread overview]
Message-ID: <200903031504.27461.vapier@gentoo.org> (raw)
In-Reply-To: <20090303075621.GD3811@comet>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Tuesday 03 March 2009 02:56:21 Donnie Berkholz wrote:
> On 23:54 Mon 02 Mar , Donnie Berkholz wrote:
> > On 01:27 Tue 03 Mar , Mike Frysinger wrote:
> > > On Monday 02 March 2009 22:56:27 Donnie Berkholz wrote:
> > > > Actually seems like quite a few of the bash-completion scripts have
> > > > issues with 4.0 ... might want to just run through those.
> > >
> > > i dont use bash completion so i dont have any actually installed. run
> > > `bash - n` on each one on your system and let me know which ones result
> > > in errors.
> >
> > for i in *; do bash -n $i || echo FAILED $i; done
>
> Meh. extglob fixes all these, including genkernel. Annoying that
> anything besides our bash-completion framework doesn't handle this right
> (because .pre isn't sourced in each script).
>
> Thanks for the pointer!
the genkernel one you pointed out originally is a bug and ive posted something
upstream for it
all the others seem to be extglob related as they use the extended pathname
expansion syntax
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-04 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 0:27 [gentoo-dev] bash-4.0-r1 for ~arch Mike Frysinger
2009-03-03 3:56 ` Donnie Berkholz
2009-03-03 6:25 ` Caleb Cushing
2009-03-03 6:39 ` Mike Frysinger
2009-03-03 6:43 ` Caleb Cushing
2009-03-03 6:27 ` Mike Frysinger
2009-03-03 6:58 ` [gentoo-dev] " ABCD
2009-03-03 7:54 ` [gentoo-dev] " Donnie Berkholz
2009-03-03 7:56 ` Donnie Berkholz
2009-03-03 20:04 ` Mike Frysinger [this message]
2009-03-03 22:55 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903031504.27461.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox