From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12892 invoked by alias); 22 Feb 2017 04:39:58 -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: 22484 Received: (qmail 26412 invoked from network); 22 Feb 2017 04:39:58 -0000 X-Qmail-Scanner-Diagnostics: from mta03.eastlink.ca by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(24.224.136.9):SA:0(-0.7/5.0):. Processed in 0.822671 secs); 22 Feb 2017 04:39:58 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: rayandrews@eastlink.ca X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.eastlink.ca designates 24.224.136.9 as permitted sender) X-Authority-Analysis: v=2.2 cv=DOfN2GFb c=1 sm=1 tr=0 a=aWG3ZaPfpGbmBTXoUM+q2Q==:117 a=aWG3ZaPfpGbmBTXoUM+q2Q==:17 a=N659UExz7-8A:10 a=l0u6BaXDHHVu2DMh5ukA:9 a=pILNOxqGKmIA:10 X-EL-IP-NOAUTH: 24.207.17.185 Subject: Re: trap ERR To: zsh-users@zsh.org References: <20170221164121.2f832559@pwslap01u.europe.root.pri> <170221093044.ZM14374@torch.brasslantern.com> <170221202133.ZM15856@torch.brasslantern.com> From: Ray Andrews Message-id: Date: Tue, 21 Feb 2017 20:39:52 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 MIME-version: 1.0 In-reply-to: <170221202133.ZM15856@torch.brasslantern.com> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit On 21/02/17 08:21 PM, Bart Schaefer wrote: > Generally speaking there are going to be some things that you don't > want to have happen in non-interactive shells, so I wouldn't suggest > blindly "mv ~/.zshrc ~/.zshenv" -- and you should be cautious about > e.g. "ssh somehost somecommand" behaving differently because somehost > has stuff in .zshenv. > I'll play with it. The first time I read about the init scripts, fact is I didn't understand the terminology used. I get it now tho.