From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7645 invoked by alias); 15 Oct 2014 01:00:39 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19259 Received: (qmail 11062 invoked from network); 15 Oct 2014 01:00:36 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_MNsiX9sJ2dTTaBTZus+qRQ)" X-Authority-Analysis: v=2.1 cv=HYUtEE08 c=1 sm=1 tr=0 a=/ugl2wLTUB9YkCDsaotiaA==:117 a=/ugl2wLTUB9YkCDsaotiaA==:17 a=sicYhokT53YA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=9iDbn-4jx3cA:10 a=cKsnjEOsciEA:10 a=ZErvbqJlFYLdsHPloVYA:9 a=QEXdDO2ut3YA:10 a=pGLkceISAAAA:8 a=1P4i9iLN3xLdU7_79y0A:9 a=h5OL0hQyRjHewEQp:21 a=_W_S_7VecoQA:10 Message-id: <543DC7B8.7000306@eastlink.ca> Date: Tue, 14 Oct 2014 18:02:48 -0700 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.0 To: Bart Schaefer Cc: Zsh Users Subject: Re: combining .histfiles References: <54397CC0.9070206@eastlink.ca> <141011131053.ZM28143@torch.brasslantern.com> <5439A54A.9060304@eastlink.ca> <141011150111.ZM28417@torch.brasslantern.com> <5439CB82.3070401@eastlink.ca> <87h9z7dc91.fsf@lwm.klanderman.net> <543C4C85.2060807@eastlink.ca> <543D5B45.1000808@eastlink.ca> <543DA2E0.8020000@eastlink.ca> In-reply-to: --Boundary_(ID_MNsiX9sJ2dTTaBTZus+qRQ) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT On 10/14/2014 04:55 PM, Bart Schaefer wrote: > > On Oct 14, 2014 3:24 PM, "Ray Andrews" > wrote: > > > > I could stop the command on each line individually, but not the > .histfile *itself*. Is there some way to > > to break out of it? > > As I said, Ctrl+c should do it. I just now manufactured a file with a > few hundred "cp largefile /dev/null" commands, read it with "." and > was able to end it with Ctrl+c before it made it all the way through. > Hmmm, it didn't work here, I hit Ctrl+c a dozen times, it didn't break out. I'll try to figure out why. > On the other hand, you are the first person I've ever heard of make > this particular mistake. :-) :-/ Well then never mind. You can be sure I'll never do it again, that is for sure! What with the file format, all those leading numbers, it didn't look executable so the worst thing is that it was such a huge shock. Never more. But it does make me question what *isn't* executable. --Boundary_(ID_MNsiX9sJ2dTTaBTZus+qRQ)--