From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19800 invoked by alias); 14 Oct 2014 22:23:37 -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: 19257 Received: (qmail 7878 invoked from network); 14 Oct 2014 22:23:25 -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,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Authority-Analysis: v=2.1 cv=AduIQRnG c=1 sm=1 tr=0 a=/ugl2wLTUB9YkCDsaotiaA==:117 a=/ugl2wLTUB9YkCDsaotiaA==:17 a=sicYhokT53YA:10 a=IkcTkHD0fZMA:10 a=gjlwMiAVmdVYZ2OZRTwA:9 a=QEXdDO2ut3YA:10 Message-id: <543DA2E0.8020000@eastlink.ca> Date: Tue, 14 Oct 2014 15:25:36 -0700 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.0 MIME-version: 1.0 To: zsh-users@zsh.org 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> In-reply-to: Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 7bit On 10/14/2014 03:04 PM, Bart Schaefer wrote: Bart, > and it merrily started executing everything in my history. > Yes, history files have historically (ahem) been kept in a format that is > readable as shell command input. I suspect this may date from early csh > implementations that reloaded the history by disabling command execution > and then running the file through the parser. I suppose there could be some good reason for it, but sheesh ... > Hmm, I don't know any reason why a regular interrupt (Ctrl+c) would > not stop "." execution, regardless of whether the script is a history > file or any other script, as long as the commands being executed are > themselves interruptible. I could stop the command on each line individually, but not the .histfile *itself*. Is there some way to to break out of it? > You mentioned a "slow copy" ... I've found that if an external command > is in disk wait state it may not respond to interrupts. Sometimes a > Ctrl+z will suspend such a job even when Ctrl+c won't kill it. I should have said 'large copy'. A system backup actually, so it gave me time to dive for the power. I hate to think of the mess that might have been made, however. If there was ever a file that should be somehow protected from running, that's it.