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

2005-07-07 Thread Chet Ramey
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] This is a

sourcing and args

2005-07-07 Thread debian_sid
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'

Re: sourcing and args

2005-07-07 Thread Paul Jarc
[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.

unable to redirect readonly variable error

2005-07-07 Thread Ian Macdonald
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

Re: unable to redirect readonly variable error

2005-07-07 Thread Ian Macdonald
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]

difference between complete -o default and -o bashdefault

2005-07-07 Thread Ian Macdonald
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

Re: unable to redirect readonly variable error

2005-07-07 Thread Chris F.A. Johnson
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

Re: unable to redirect readonly variable error

2005-07-07 Thread Felipe Kellermann
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

Re: unable to redirect readonly variable error

2005-07-07 Thread Chris F.A. Johnson
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]$

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

2005-07-07 Thread Jochen Baier
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