Re: [completion with directory starting with = doesn't work]

Tatavarty Kalyan wrote: > I see the same behaviour as posted above. > > # mkdir =foo =foobar > # cd =\=foo > -bash: cd: ==foo: No such file or directory This is part of the bash_completion extensions. I forget now but I remember at one time thinking I understood the issues. It is related to it

Re: [completion with directory starting with = doesn't work]

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

Re: Broken parse on `'${'`

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Lev Bishop on 7/7/2005 9:50 PM: >>bash$ echo `echo '${'` >> > > Actually, this is a bad example, because even if bash did parse > correctly, there would be still an incomplete ${ substitution for the > outer echo No, because by POSIX XCU

Broken parse on `'${'`

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Configuration Information [Automatically generated, do not change]: Machine: i686 OS: cygwin Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' - -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin' -DCONF_VENDOR='pc' - -

Re: (feature request) separate history for each folder / folder related history

On Thu, 7 Jul 2005, Jochen Baier wrote: hi, do you already thought about to have a folder related history ? for example: in folder: code/superprogram: i use the commands: make, ./superprogram in folder: code/homepage: i use "scp index.html [EMAIL PROTECTED]" to upload the next day, i go to

Re: [completion with directory starting with = doesn't work]

Chet Ramey a écrit : Machine Type: i586-mandrake-linux-gnu Bash Version: 2.05b Patch Level: 0 Release Status: release Description: [Hello, whenever I hit tab to have completion on a directory whose name start by = i got that : cd =\=Boulot bash: cd: ==Boulot: No such file or director]

(feature request) separate history for each folder / folder related history

hi, do you already thought about to have a folder related history ? for example: in folder: code/superprogram: i use the commands: make, ./superprogram in folder: code/homepage: i use "scp index.html [EMAIL PROTECTED]" to upload the next day, i go to "code/superprogram" folder and the bash hi

Re: unable to redirect readonly variable error

On Thu, 7 Jul 2005, Ian Macdonald wrote: On Thu 07 Jul 2005 at 20:07:33 -0400, you wrote: On Thu, 7 Jul 2005, Ian Macdonald wrote: Hello, This doesn't seem right: [EMAIL PROTECTED] bash_completion]$ foo=x [EMAIL PROTECTED] bash_completion]$ foo=bar [EMAIL PROTECTED] bash_completion]$ readonl

Re: unable to redirect readonly variable error

On Thu, 7 Jul 2005 4:58pm -0700, Ian Macdonald wrote: > [EMAIL PROTECTED] bash_completion]$ foo=bar 2>/dev/null > bash: foo: readonly variable $ { foo=bar; } 2> /dev/null -- Felipe Kellermann ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.

Re: unable to redirect readonly variable error

On Thu, 7 Jul 2005, Ian Macdonald wrote: Hello, This doesn't seem right: [EMAIL PROTECTED] bash_completion]$ foo=x [EMAIL PROTECTED] bash_completion]$ foo=bar [EMAIL PROTECTED] bash_completion]$ readonly foo [EMAIL PROTECTED] bash_completion]$ foo=bar >/dev/null bash: foo: readonly variable [E

difference between complete -o default and -o bashdefault

Hello, I can't quite work out what the difference is between -o default and -o bashdefault. One is readline-oriented and the other is not, but the effect appears to be the same for the cases that I have run through. Anyone? Ian -- Ian Macdonald | The one good thing about repeating

Re: unable to redirect readonly variable error

On Thu 07 Jul 2005 at 20:07:33 -0400, you wrote: > On Thu, 7 Jul 2005, Ian Macdonald wrote: > > >Hello, > >This doesn't seem right: > >[EMAIL PROTECTED] bash_completion]$ foo=x > >[EMAIL PROTECTED] bash_completion]$ foo=bar > >[EMAIL PROTECTED] bash_completion]$ readonly foo > >[EMAIL PROTECTED]

unable to redirect readonly variable error

Hello, This doesn't seem right: [EMAIL PROTECTED] bash_completion]$ foo=x [EMAIL PROTECTED] bash_completion]$ foo=bar [EMAIL PROTECTED] bash_completion]$ readonly foo [EMAIL PROTECTED] bash_completion]$ foo=bar >/dev/null bash: foo: readonly variable [EMAIL PROTECTED] bash_completion]$ foo=bar 2>

Re: sourcing and args

[EMAIL PROTECTED] wrote: > When sourcing a bash script from a 'parent' script the > parameters/args supplied to the 'parent' script are passed > on to the sourced script (!) This is the traditional behavior, required for compatibility with other shells and existing scripts.

sourcing and args

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba

Re: [completion with directory starting with = doesn't work]

> Machine Type: i586-mandrake-linux-gnu > > Bash Version: 2.05b > Patch Level: 0 > Release Status: release > > Description: > [Hello, whenever I hit tab to have completion on a directory whose > name start by = i got that : > > cd =\=Boulot > bash: cd: ==Boulot: No such file or director] Th