There appears to be some problem with wolfberry.srv.cs.cmu.edu
repeating emails. I have enabled emergency moderation on the mailing
list for a bit hoping to avoid further repeats while this problem gets
fixed. This will cause additional delay to all postings until the
problem is resolved.
Bob
>bash --version
>GNU bash, version 4.1.7(1)-release (i586-pc-interix3.5)
#! /usr/local/bin/bash
one=`cat data`
echo one=$one
two=$(cat data)
echo two=$two
>one=abc
>./xs: command substitution: line 7: syntax error near unexpected token `)'
>./xs: command substitution: line 7: `cat data)'
>two
Greg Wooledge wrote:
> In this particular case, I would use a glob rather than an ERE,
> because "h?" is much simpler than "^h.$".
Besides, bash's extended globs provide everything ERE's provide. I use
the idiom:
shopt -s extglob
# for example, to check for numbers
case "-${somethin
while is a compound command. Only simple commands can have preceding
variable assignments. From man bash:
The environment for any simple command or function may be augmented
temporarily by prefixing it with parameter assignments, as described
above in PARAMETERS. These assignment statement
Bash Version: 4.0
Patch Level: 35
Release Status: release
Description:
I am used to setting variables in front of a command like in
> LANG=C man mplayer
However, I get a "bash: syntax error near unexpected token `do'" error
when trying:
> FOO=BAR while read a b; do echo $a $b; done
Why? Th
On Thu, Aug 05, 2010 at 10:09:38AM +, Dimitar DIMITROV wrote:
> The extended glob pattern @(?|??|???|)*([[:space:]]):*([[:space:]])
> is not respected when used for the HISTIGNORE environment variable:
>
> export HISTIGNORE='@(?|??|???|)*([[:space:]]):*([[:space:]])'
This
> On Thu, Aug 05, 2010 at 10:09:38AM +, Dimitar DIMITROV wrote:
> >The extended glob pattern @(?|??|???|)*([[:space:]]):*([[:space:]])
> >is not respected when used for the HISTIGNORE environment variable:
> >
> >export HISTIGNORE='@(?|??|???|)*([[:space:]]):*([[:space:]])'
Configuration Information:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i68 ↪ 6-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
>>This is "much more code":
>>
>> F(){ find "$@"; }
>>
> This simple func definition will be 4 lines in my coding style. :) And I
> like adding at least one blank line between functions.
Then just exclude .bashrc from your coding style.
