From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23694 invoked by alias); 24 Sep 2010 14:18:54 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 28290 Received: (qmail 6805 invoked from network); 24 Sep 2010 14:18:52 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 Received-SPF: pass (ns1.primenet.com.au: SPF record at benizi.com designates 64.130.10.15 as permitted sender) Date: Fri, 24 Sep 2010 10:18:23 -0400 (EDT) From: "Benjamin R. Haskell" To: Peter Stephenson cc: Zsh Workers Subject: Re: !!$ unitialized at first prompt In-Reply-To: <20100924133936.245765b2@pwslap01u.europe.root.pri> Message-ID: References: <20100924133936.245765b2@pwslap01u.europe.root.pri> User-Agent: Alpine 2.01 (LNX 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Fri, 24 Sep 2010, Peter Stephenson wrote: > The shell doesn't split words in the same way when importing history. > In normal operation it relies on the lines having been passed through > the lexical analyser to generate the words, which doesn't happen when > history is read from a file. Instead it just blindly splits on > whitespace. Interesting. I'm surprised it splits the history when it's read in. (I would've expected it to read in whole command lines and only split into words when necessary.) But, glad there's a simple explanation. -- Thanks, Ben