Hi all,
Strange condition that i can't find the solution to.
My bash for RH 3.4.6, is 3.00.15(1)
I have a .inputrc file with some settings like
"\C-w": kill-region
"\M-u": upcase-word
The \C-w bind is different than the default ( which is to unix-word-
rubout )
I can change this by doing a
Hi all,
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: darwin9.0
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -
DCONF_OSTYPE='dar\
win9.0' -DCONF_MACHTYPE='i386-apple-darwin9.0' -DCONF_VENDOR='apple' -
DLOCALEDI\
R='/usr/share
On Tuesday 03 March 2009 17:14:16 Chet Ramey wrote:
> Mike Frysinger wrote:
> > On Tuesday 03 March 2009 15:28:28 Chet Ramey wrote:
> >> Mike Frysinger wrote:
> >>> code that uses case statements in a subshell and then uses comments
> >>> causes bash to trigger a parsing error:
> >>> $ cat test.sh
Mike Frysinger wrote:
> On Tuesday 03 March 2009 15:28:28 Chet Ramey wrote:
>> Mike Frysinger wrote:
>>> code that uses case statements in a subshell and then uses comments
>>> causes bash to trigger a parsing error:
>>> $ cat test.sh
>>> echo $(case a in (a) echo ok ;; # comment
>>> )
>>> $ sh ./t
On Tuesday 03 March 2009 15:28:28 Chet Ramey wrote:
> Mike Frysinger wrote:
> > code that uses case statements in a subshell and then uses comments
> > causes bash to trigger a parsing error:
> > $ cat test.sh
> > echo $(case a in (a) echo ok ;; # comment
> > )
> > $ sh ./test.sh
> > ./test.sh: lin
Mike Frysinger wrote:
> code that uses case statements in a subshell and then uses comments causes
> bash to trigger a parsing error:
> $ cat test.sh
> echo $(case a in (a) echo ok ;; # comment
> )
> $ sh ./test.sh
> ./test.sh: line 1: unexpected EOF while looking for matching `)'
> ./test.sh: lin
Hi,
I have no root access to a server, so I can only install bashdb under my
$HOME. Unfortunately bashdb requires Bash 3.1 or 3.2 but the bash on the
server is version 3.00.15. So I first installed bash 3.2 under my
$HOME/bin/bash-3.2.48
/bin/ from its source. Then I run configuration of dashdb a
Got it. Thank you very much!
--
View this message in context:
http://www.nabble.com/order-of-redirections-tp22298397p22316124.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
smallnow wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
> -DCONF_VENDOR='unknown' -
