From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27930 invoked by alias); 7 Mar 2015 07:20:42 -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: 34675 Received: (qmail 22396 invoked from network); 7 Mar 2015 07:20:31 -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:mime-version:content-type; bh=5MUR6Ty3Yjm3DjKajipLuLptP4PUchGGALrepCMQIS4=; b=FOG/gG4aS/j709FAvNfJEzfeWZAfgJyemLWWrpOxUaoSvGvNJjYNxiAqexcB1ISTOa d89ImyklajyAWuAlXGu0XU1w+kcanfqn8MP1JMiWJJK8wtWGuNrrZj07MvzrScMPPmu0 7QaK4CTQeUwtsff80BMs40DODsgd1TXIa0hwcOKMVbV+wRzdiYh6rS6/JIMy1vxHjMDZ G7n+kyBON/welfWUqrXuIAV5qJYsP3rT30IBCI85jwPAnSeQzEm4fHiHIgAC9Y1XPyB2 31nTqK7OqZuX4JCWz4xcuzTEq3OewGgHxPn3OD2QkkEiQffb2GnMiwzW6IAo/6rmEocu rbgw== X-Gm-Message-State: ALoCoQmyQazft4Vvh8u6AUzAlmEPzI4AhLYrpJxkYYmyR7oYm7JMqB7qPWNFzL79G9pcSYA0ZX+z X-Received: by 10.202.98.197 with SMTP id w188mr13130494oib.6.1425712827602; Fri, 06 Mar 2015 23:20:27 -0800 (PST) From: Bart Schaefer Message-Id: <150306232024.ZM12511@torch.brasslantern.com> Date: Fri, 6 Mar 2015 23:20:24 -0800 In-Reply-To: <54FA731B.8050800@pobox.com> Comments: In reply to Andrew Janke "FAQ title bar answer using chpwd()" (Mar 6, 10:40pm) References: <54FA731B.8050800@pobox.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Andrew Janke , zsh-workers@zsh.org Subject: Re: FAQ title bar answer using chpwd() MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 6, 10:40pm, Andrew Janke wrote: } } http://zsh.sourceforge.net/FAQ/zshfaq03.html#l23 } } Answer 3.6 suggests using chpwd() to emit terminal control sequences to } update the title bar for Apple's Terminal.app. This probably isn't the } right place to do it, because cd's can happen inside functions, } pipelines, and so on whose output is going to be captured for use } elsewhere. The terminal control sequences will contaminate the captured } output instead of going to the terminal. If you've actually examined the FAQ example, you'll see [[ -t 1 ]] || return which means to do nothing if the standard output is not a terminal. That's a perfectly reasonable solution to the issue described here: } https://github.com/robbyrussell/oh-my-zsh/issues/3524 In short, the FAQ answer is correct and whoever created the chpwd to which that issue refers, has coded it wrong.