Re: difference between complete -o default and -o bashdefault

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

--with-installed-readline breaks tilde-expansion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On the cygwin list, a difference was pointed out between compilations of bash that avoid or use --with-installed-readline: static_bash$ echo $HOME ~ /home/eblake /home/eblake static_bash$ HOME=/tmp; echo $HOME ~ /tmp /tmp dynamic_bash$ echo $HOME ~ /

add PS1 to messages?

Not sure if there is any fix for this. When sending messages like "Terminated" to the terminal, maybe also send a PS1, if indeed we are in prompt waiting foreground mode or whatever. Don't just leave the users cursor parked at column 1: # PS1="# " # sleep 33& [1] 3355 # killall sleep # [1]+ Termin

Re: unable to redirect readonly variable error

Ian Macdonald wrote: > Hello, > > This doesn't seem right: If no command name results after word expansion, variable assignments take place in the current shell environment, and rediretions take place in a subshell environment. The variable assignments are attempted first. Chet -- ``The lyf so

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 > # 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 relate