=~ behaves differently in bash 3.2 and 3.0

In bash 3.0.14, the condition [[ file.txt =~ .*\\.txt\$ ]] returns TRUE but in 3.2.39 it returns FALSE. But with the shopt option `compat31' set it also returns TRUE. Is that reasonable? In the bash manual, `compat31' makes sense only for quoted patterns. The string .*\\.txt\$ is considered to be q

Re: ssh changed from socket to pipe stdin

If you can, make the target of your ssh invocation a wrapper script that sources .bashrc and then executes the remaining arguments. Something like (in /usr/bin/local/ssh-target.sh): #!/usr/bin/env bash .[ -f ~/.bashrc ] && . ~/.bashrc "$@" ssh [EMAIL PROTECTED] /usr/local/bin/ssh-target.sh cmd

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

Serge Dussud - Sun Microsystems wrote: > -z interpose > > . > > > Could it be the explanation and a possible solution ? Well, let's try it. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~c

Re: ssh changed from socket to pipe stdin

> and with this change .bashrc is never sourced. Will we do something with > this? Changing check from socket to pipe stdin will cause problems with > older ssh. Maybe defining SSH_SOURCE_BASHRC? Or just don't do anything? This is the reaason that SSH_SOURCE_BASHRC exists, but you have to accept

Re: ssh changed from socket to pipe stdin

Roman Rakus wrote: and with this change .bashrc is never sourced. Will we do something with this? Changing check from socket to pipe stdin will cause problems with older ssh. Maybe defining SSH_SOURCE_BASHRC? Or just don't do anything? RR This is invoked by https://bugzilla.redhat.com/show_

ssh changed from socket to pipe stdin

and with this change .bashrc is never sourced. Will we do something with this? Changing check from socket to pipe stdin will cause problems with older ssh. Maybe defining SSH_SOURCE_BASHRC? Or just don't do anything? RR