Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Qmail-Scanner-Diagnostics: from mail-vk0-f53.google.com by f.primenet.com.au (envelope-from <peetnick2@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.213.53):SA:0(0.3/5.0):. 
 Processed in 0.140041 secs); 15 Jul 2016 15:08:07 -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.3 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,
	FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_DKIM_INVALID autolearn=no
	autolearn_force=no version=3.4.1
X-Envelope-From: peetnick2@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.213.53 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to;
        bh=ksDflBhj2hIgwFLQU+rnA5dZpUJIP5vOipNbdEIrFJA=;
        b=bS77+UVXjsrGoVb8MEPHQwA+Ujmdxmh68HKjX3ETiQ1y70NaUD7BA/M/2zYl7PL/o2
         mSiTrwEr1ZEjsVmBdMWiQZiHowlda2cUsfERidJD3S47oZAHMWjxUOJNOytB/DBgKjA3
         4fHDYNYLdfYG/gXJIzTIifDR+VtmvXmD5dIQ/ebJ4lrHcNLSVPnADZ2GdH6D1HbFlnPS
         DUI/XZvg8HY9ZTrkJUdoAmWXz7t4DUQuD4WHGGHSZoF3Up5sJ3Lyhu+W9nfhU5ZWRHdU
         d5/ovarTBsYiE6g6599llOR/SjS94cQUgbAE65yNxPcXw6z4WkKV0+aDzA7f387a2eDI
         Ni4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=ksDflBhj2hIgwFLQU+rnA5dZpUJIP5vOipNbdEIrFJA=;
        b=SZb/hYdnPSMPcMIYb2BPlGkgOcqedw1BSwYklB/9FWrhEwibR85BDYxLLeZR6iCoQZ
         rVgaiMSDNsSKfaRu9xZF/FdzPs1/aWAstTsZsyS30P4NVCLJU/jS5EQYNk2DohEltzob
         frWVjUPrUDj7e2g2e/YccbAM5xnzUVIhf5++dsBsADZJCo5e8sLMAQ52JwliWt2PRkm1
         9WGT2OP8nOEJmeEX6y9o68tr7uPB+TQ6oBLfFxE2odeAxxUGtVE3JYczLqzOHw1z68at
         tGNKrdqmLK9pV22dZy9YBu6Ker11YOoMOa4rXAYY95ycKKN6JYKQDxfOb33FZHxiasXr
         oqmA==
X-Gm-Message-State: ALyK8tJGrIW4a3QQkVYcXXmVpO6riCUwBNNxUsNujxj9RHTr0dOb2z96j8BiHVyV7likHTw2zr9h52ZUFC5PpA==
X-Received: by 10.159.32.227 with SMTP id 90mr10276442uaa.85.1468593659033;
 Fri, 15 Jul 2016 07:40:59 -0700 (PDT)
MIME-Version: 1.0
From: Peet Nick <peetnick2@gmail.com>
Date: Fri, 15 Jul 2016 16:40:58 +0200
Message-ID: <CAJwqTS8XHV_hCER9t5B2VgLqidH5wMmKbQC7=+CWkkW0abnMXg@mail.gmail.com>
Subject: [BUG/IMPROVEMENT] Buffer corruption while horizontally resizing
 terminal window
To: zsh-workers@zsh.org
Content-Type: multipart/alternative; boundary=94eb2c0b76ea5ddbf10537ad9bea
X-Seq: zsh-workers 38858

--94eb2c0b76ea5ddbf10537ad9bea
Content-Type: text/plain; charset=UTF-8

Hey,

I am having the following issue that the buffer gets corrupted when
horizontally resizing the terminal window.

For reference please see this thread:
https://bbs.archlinux.org/viewtopic.php?id=214830

Screenshot:
https://s32.postimg.org/6hws6v39x/Screenshot_from_2016_07_13_23_15_31.png

A user pointed out that it is caused by "zle reset-prompt".

Is this intentional behavior that the old buffer gets corrupted when
resizing the window?

--94eb2c0b76ea5ddbf10537ad9bea--