Re: Administrivia: Repeated Emails

2010-08-09 Thread Bob Proulx
Bob Proulx wrote: > 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 >

Wrong prompt and incorrect parsing if completion is used

2010-08-09 Thread Egmont Koblinger
Hello, I've found a weird behavior. In some circumstances, if I use TAB completion during typing a command line, the final command is parsed differently than if I typed it all along. I'm on Ubuntu Lucid. The bug described below occurs only if I use the bash-completion package (that is, I source

history -a

2010-08-09 Thread Bruce Korb
My history file isn't being updated as I am led to believe it ought to be. Is there some shopt or other thingey that keeps the history unwritten? I've googled the issue and the answer is supposed to be "history -a", on occasion, but that isn't working: $ ls -l $HISTFILE;history;history -a;ls -l $H

Re: syntax error when setting variable in front of "while"

2010-08-09 Thread Chet Ramey
On 8/8/10 10:17 PM, mfwit...@gmail.com wrote: > Interestingly, according to: > > info bash 'Basic Shell Features' 'Shell Commands' Pipelines > > we have: > > A `pipeline' is a sequence of simple commands separated > by one of the control operators `|' or `|&'. Sorry, the `simple' should

Re: bash 4.1 command substitution

2010-08-09 Thread Chet Ramey
On 8/7/10 8:02 PM, John Kelly wrote: > On Fri, 06 Aug 2010 17:31:08 +, John Kelly wrote: > >>> bash --version >>> GNU bash, version 4.1.7(1)-release (i586-pc-interix3.5) > >> Backquote command substitution works, but $(...) does not. > >> I built it like this: > >>> CFLAGS="-O2 -march=i686

Re: bash 4.1 command substitution

2010-08-09 Thread John Kelly
On Fri, 06 Aug 2010 17:31:08 +, John Kelly wrote: >>bash --version >>GNU bash, version 4.1.7(1)-release (i586-pc-interix3.5) >Backquote command substitution works, but $(...) does not. >I built it like this: >>CFLAGS="-O2 -march=i686" \ >>./configure \ >>--mandir=/usr/local/man \ >>

Re: RFE: allow double quotes to group multi-words & be treated?as?1?arg, w/DQ's stripped off -- including RH =~

2010-08-09 Thread clemens fischer
clemens fischer wrote: > [...] If you received several emails/posts, I apologize. This was a problem with "news.eternal-september.org". My article was sent only once from my box. clemens

Re: bash 4.1 command substitution

2010-08-09 Thread Dennis Williamson
I can't reproduce your problem. Does this work?: three=$(< data) echo three=$three On Fri, Aug 6, 2010 at 12:31 PM, John Kelly wrote: > >>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) > e

Re: syntax error when setting variable in front of "while"

2010-08-09 Thread Ralf Goertz
Dennis Williamson wrote: > while is a compound command. Only simple commands can have preceding > variable assignments. From man bash: Thanks. I just found out that I can get away with > while IFS=$'\t' read a b; do echo "$a" "$b"; done

Re: syntax error when setting variable in front of "while"

2010-08-09 Thread mfwitten
On Fri, Aug 6, 2010 at 5:40 AM, Ralf Goertz wrote: >> 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 >> tok