if you use "$PWD" variable the assignment seems redundant too:)
On 11/14/07, Mike Stroyan <[EMAIL PROTECTED]> wrote:
>
> On Wed, Nov 14, 2007 at 01:11:12PM +0800, 龙海涛 wrote:
> > it works.
> > 3x very much.
> >
> > On Tue, 2007-11-13 at 21:51 -0700, Bob Proulx wrote:
> >
> > > 龙海涛 wrote:
> > > > i
On 9/8/06, Alexander Elgert <[EMAIL PROTECTED]> wrote:
Tatavarty Kalyan schrieb am 07.09.2006 um 14:20:43 (+0800):
> On 9/6/06, Chris F.A. Johnson <[EMAIL PROTECTED]> wrote:
> >
> >On 2006-09-06, Andreas Schwab wrote:
> >> [EMAIL PROTECTED] (Paul Jarc) write
On 9/6/06, Chris F.A. Johnson <[EMAIL PROTECTED]> wrote:
On 2006-09-06, Andreas Schwab wrote:
> [EMAIL PROTECTED] (Paul Jarc) writes:
>
>> Mike Frysinger <[EMAIL PROTECTED]> wrote:
>>> this little bit of code doesnt work right:
>>> foo() { echo "${1:-a{b,c}}" ; }
The first '}' is interpreted
Please try, "ls a[[:upper:]]a" instead.
"a[:upper:]a" matches 'a' followed by any one of ':','u','p','e','r'
,followed by 'a'.
Thanks,
Kalyan
On 7/22/05, James Downs <[EMAIL PROTECTED]> wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i386
> OS: linux-gnu
Though I get the same results as posted above on i686,i am not sure if
this is a bash problem.
On the other hand i feel there is might be some issue with the glibc
read and /proc filesystem on some 2.6 kernels as i wasnt able to
reproduce this on Redhat with 2.4.21-20.EL kernel.I was able to
r
I think bashdefault tries out username,hostname,command word,glob
completions where as 'default' just tries out filename completions.
On 7/8/05, Ian Macdonald <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I can't quite work out what the difference is between -o default and -o
> bashdefault. One is re
I see the same behaviour as posted above.
# mkdir =foo =foobar
# cd =\=foo
-bash: cd: ==foo: No such file or directory
# echo $BASH_VERSION
2.05b.0(1)-release
I get the same result with bash version 3.00.15(1)-release.
I am not sure if this is related to bash completion package.
Also this maynot
