Re: Pathname expansion not performed in Here Documents

2012-02-27 Thread Steven W. Orr
On 2/27/2012 1:26 AM, Pierre Gaston wrote: On Mon, Feb 27, 2012 at 6:44 AM, Davide Baldini wrote: On 02/27/12 05:04, DJ Mills wrote: Think of regular here-doc (with an unquoted word) as being treated the same way as a double-quoted string Thank you Mills, of course I can understand it _now_

Re: Pathname expansion not performed in Here Documents

2012-02-27 Thread Pierre Gaston
On Mon, Feb 27, 2012 at 2:50 PM, Steven W. Orr wrote: > On 2/27/2012 1:26 AM, Pierre Gaston wrote: >> >> On Mon, Feb 27, 2012 at 6:44 AM, Davide Baldini >>  wrote: >>> >>> On 02/27/12 05:04, DJ Mills wrote: Think of regular here-doc (with an unquoted word) as being treated the same

Re: Pathname expansion not performed in Here Documents

2012-02-27 Thread Davide Baldini
On 02/27/12 07:26, Pierre Gaston wrote: > The manual seems quite clear: > "If word is unquoted, all lines of the here-document are subjected to > parameter expansion, command substitution, and arithmetic > expansion. In the latter case, the character sequence \ is > ignored, and \ must be used

Fwd: Re: shopt can't set extglob in a sub-shell?

2012-02-27 Thread Davide Baldini
Original Message Subject: Re: shopt can't set extglob in a sub-shell? Date: Mon, 27 Feb 2012 04:50:15 +0100 From: Davide Baldini <*@gmail.com> Organization: Aioe.org NNTP Server Newsgroups: gnu.bash.bug [...] On 02/26/12 12:41, John Kearney wrote: > I updated that wiki page > Hop

Re: Pathname expansion not performed in Here Documents

2012-02-27 Thread Roman Rakus
On 02/27/2012 01:50 PM, Steven W. Orr wrote: I don't mean this in a snarky way, but shell man pages are historically in the class of docs that you really need to read over and over again. There are a few books on shell programming, most of them not very good, but I personally have read the bash

Re: Pathname expansion not performed in Here Documents

2012-02-27 Thread Chet Ramey
On 2/27/12 8:07 AM, Davide Baldini wrote: >> "If word is unquoted, all lines of the here-document are subjected to >> parameter expansion, command substitution, and arithmetic expansion." >> >> No pathname expansion. > > That section of manual doesn't specifically include word splitting nor > pa

Re: Pathname expansion not performed in Here Documents

2012-02-27 Thread Dan Douglas
On Monday, February 27, 2012 02:07:25 PM Davide Baldini wrote: > FROM Davide Baldini > > On 02/27/12 04:11, Dan Douglas wrote: > > "If word is unquoted, all lines of the here-document are subjected to > > parameter expansion, command substitution, and arithmetic expansion." > > > > No pathname ex

previous command v whitespace following prompt

2012-02-27 Thread Duarte Fusco
hi I do this: $ ls a a $ls b b then I press C-p and I get $ ls a I put some whitespace following the prompt before typing ls b. I was expecting to get the previous command but it gave me the before previous one. Is this a bug? best regards Duarte

Re: previous command v whitespace following prompt

2012-02-27 Thread Greg Wooledge
On Mon, Feb 27, 2012 at 07:59:41PM +0100, Duarte Fusco wrote: > I put some whitespace following the prompt before typing ls b. > I was expecting to get the previous command but it gave me the before > previous one. HISTCONTROL A colon-separated list of values controlling how comm

Re: previous command v whitespace following prompt

2012-02-27 Thread Eric Blake
On 02/27/2012 11:59 AM, Duarte Fusco wrote: > hi > > I do this: > $ ls a > a > $ls b > b > > then I press C-p and I get > $ ls a > > I put some whitespace following the prompt before typing ls b. > I was expecting to get the previous command but it gave me the before > previous one. > I