From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 205 invoked by alias); 25 Sep 2011 23:38: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: 16430 Received: (qmail 3160 invoked from network); 25 Sep 2011 23:37:48 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.210.41 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ValOtIqi+EaTC42hvpuDl0psR0/b5rv/zo5jPZFNfHs=; b=cDk9H/7oE6EhPO3LbsrPuJqpcz9I3b/T6XQHyZuyLHUwr7sXcD0Pp3dPmyIs4O7jsP BDofv4oZ8Hfna5/b1v6VC+eS8ItA7JgNs0yrER90gjxXrZRzgD7qvTVrubIOmAeMCq7o dgId07TMNLK7IpB2ZDH+clKJZZPWcWXoq7UUg= MIME-Version: 1.0 In-Reply-To: <110925151330.ZM20235@torch.brasslantern.com> References: <110924112412.ZM24918@torch.brasslantern.com> <110925151330.ZM20235@torch.brasslantern.com> Date: Sun, 25 Sep 2011 16:31:59 -0700 Message-ID: Subject: Re: prompts with newlines get printed twice From: =?UTF-8?Q?Jorge_Israel_Pe=C3=B1a?= To: Bart Schaefer Cc: zsh-users@zsh.org Content-Type: multipart/alternative; boundary=bcaec51dde39e8a56904adcc7293 --bcaec51dde39e8a56904adcc7293 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks for your time Bart. I have tested your workaround and it does seem to work! This seems better because there is no need to wrap the prompt directive in a function or any of that stuff. I saw your post on the workers mailing list, thanks again for taking the time to look into it. Hopefully now that you've brought attention to this i= t could be discussed by people more knowledgeable with the zsh source and perhaps even get it fixed. For now I'm glad I have a workaround I can use in .zshrc at least :) Thanks again! On Sun, Sep 25, 2011 at 3:13 PM, Bart Schaefer w= rote: > On Sep 24, 4:24pm, Jorge Israel Pena wrote: > } > } So are there any known workarounds? Or is this something that would > } have to be fixed in zsh itself? > > Until a few minutes ago I'd have said it was something that needed to > be fixed in Terminal, but I may have found a zsh bug that's behind it > all. I've sent a possible fix to zsh-workers for discussion. > > On Sep 24, 5:14pm, Jorge Israel Pena wrote: > } > } Hey guys. I have extracted what I felt were the relevant parts from my > } previously posted link. Like I said, I am no zsh expert (In fact I'm > } completely new to it) so I don't know if this is right or if there are > } more efficient, better ways of doing this. > } > } Source: https://gist.github.com/1240023 > } > } I tested it various times and it seems to be working perfectly. > > I don't find any evidence that this helps except possibly by waiting to > change the prompt until the first time the WINCH is received, which > would avoid the startup-time double prompt. I still get the prompt > printed multiple times if I later resize the window. > > However, > > trap 'tput cuu1' WINCH > > (that is, move up one line on each WINCH signal) might work around it > for you. If your prompt has more than two lines, you'll need to move > up one less than the number of lines in the prompt. > --=20 - Jorge Israel Pe=C3=B1a --bcaec51dde39e8a56904adcc7293--