From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23030 invoked by alias); 7 Nov 2015 21:16:00 -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: 20931 Received: (qmail 27874 invoked from network); 7 Nov 2015 21:15:56 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00,RCVD_NUMERIC_HELO, T_FSL_HELO_BARE_IP_2 autolearn=no autolearn_force=no version=3.4.0 X-Injected-Via-Gmane: http://gmane.org/ To: zsh-users@zsh.org From: zzapper Subject: Re: FYPI zsh 5.1.1 (cygwin) broke my .zshrc Date: Sat, 7 Nov 2015 21:15:41 +0000 (UTC) Organization: Your Company Message-ID: References: <151107091222.ZM24119@torch.brasslantern.com> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 2.30.59.155 User-Agent: Xnews/2009.05.01 X-Antivirus: avast! (VPS 151107-0, 07/11/2015), Outbound message X-Antivirus-Status: Clean Bart Schaefer wrote in news:151107091222.ZM24119@torch.brasslantern.com: > > That should be perfectly valid syntax, which makes me suspect > something else is going awry that is accidentally fixed by introducing > an additional close-paren. It'd be instructive to look at "setopt > verbose" or perhaps "setopt xtrace" output of the failing .zshrc, or > you can try gradually removing bits of that .zshrc until you find the > specific thing that's going wrong. > Bart, That's useful guidance. I know I do one tricky thing I've always been unhappy with : I use a nested alias to "duplicate" script sections, can't remember why an alias and not a function. (probably explains the line number being longer than my .zshrc) -- zzapper https://twitter.com/dailyzshtip --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus