From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11590 invoked by alias); 7 Mar 2015 07:33:19 -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: 34676 Received: (qmail 4676 invoked from network); 7 Mar 2015 07:33:18 -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-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:cc:mime-version:content-type; bh=+nLRQaiDGGr7MMfjmHlcoERSkwbpUG21Ceguj9i/smI=; b=XxC0eyTHjdRMB71dq5zgb5Z5d4OJQ5p1Txdmp22P7TvvHwNIAKpiMZwcVgzp91oOhu WgkNiXavFj5hipnLBMGLgouHDCvSIgpXEV2uB7kVjfPsfzlpzF3P8bVgeEpm0eK1HGOy CBJX79nKzy8BmFE9jkFHLOh7zZdIDFxX/1Fs123BOlHwjBJNIEhslyRmgZ62YA335jDn nNiAB//xwio7mxKYwcB3g7WKRxn842odP3z/Ml9Jxs94juLa2/Mtbw9tS5bYCWw67e76 0MraH5YKzvzupkowa0xTg8UglNbuV5mvgwi9GrA47YnfuYPK5QOLDzSu65/EuThvESy1 rfJg== X-Gm-Message-State: ALoCoQl4Ump7tAAMXj+xox6un4/gVyeIUSUIkqhsZXvccS5nE/EewfB6bYxgBGs9gSFgjGyxlsWm X-Received: by 10.202.222.132 with SMTP id v126mr12984077oig.103.1425713595053; Fri, 06 Mar 2015 23:33:15 -0800 (PST) From: Bart Schaefer Message-Id: <150306233311.ZM12524@torch.brasslantern.com> Date: Fri, 6 Mar 2015 23:33:11 -0800 In-Reply-To: <20150307041924.GD2206@tarsus.local2> Comments: In reply to Daniel Shahaf "Re: FAQ title bar answer using chpwd()" (Mar 7, 4:19am) References: <54FA731B.8050800@pobox.com> <20150307041924.GD2206@tarsus.local2> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: FAQ title bar answer using chpwd() Cc: Andrew Janke MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 7, 4:19am, Daniel Shahaf wrote: } } We had a similar issue at Subversion: http://svn.apache.org/r1643793 OK, so the real problem is that - there exists some software written for the user's shell to execute - that software needs to change working directory - the user is an idiot who has installed a chpwd function that always prints to stdout - this breaks the software and is reported as a bug to the developer. Frankly I don't think any update to the zsh FAQ is going to eliminate idiocy. The developer needs to either use "cd -q ..." if the shell is known to be zsh, or to use "{ cd ... } >/dev/null" if zsh-ness for some reason is not testable.