From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id c58026f8 for ; Tue, 16 Jul 2019 22:13:13 +0000 (UTC) Received: (qmail 23438 invoked by alias); 16 Jul 2019 22:13:03 -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: List-Unsubscribe: X-Seq: 24071 Received: (qmail 2298 invoked by uid 1010); 16 Jul 2019 22:13:03 -0000 X-Qmail-Scanner-Diagnostics: from mail-vs1-f47.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25510. spamassassin: 3.4.2. Clear:RC:0(209.85.217.47):SA:0(-2.0/5.0):. Processed in 2.304802 secs); 16 Jul 2019 22:13:03 -0000 X-Envelope-From: sgniazdowski@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.217.47 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N9fJ7Vce/6JMsA5cSOf/uwiePpPda/jCgHNykxyuLro=; b=RUvRzIanB018Oled5leqKJo9BKYxZAQgBED6b3HrSiPWNOHKSwxE0Ft3ysIZnEEbk+ A+XFZV4yaEtpw8hY1ysBl3btWObzWsWFe6WpYpjadszotA5/fFxLn3oH+f58kzJFhBS6 jUNSGqB17Pm+xDO+4ykvAnyVWdBfxywZ4qN4+K5Z3+T+2A9XPyuwkB6w/0APermoCuH3 LP8u3Sh+V3xgxDPYJ7dViw+AdWsiqmrrXZ3AQ6TkGKeXwODxZrq3Bmo1QpT5qVP4FTj1 xnCqXi3EabrMqreHsoMUaYQbdQUqnnXspR46ae+m8e7QAV/DeK+DoSb/6yD6NPU5R2k1 va6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N9fJ7Vce/6JMsA5cSOf/uwiePpPda/jCgHNykxyuLro=; b=tGlUgq3izszR+7rjBsfAVwg5VGw68Q8lR9WYrAtzVmu2XfnTpgc3Y+F+tUZyUUabv7 3Qfx++79P3x2P+7ztSDcG9W2Trs2awmPCm67S8I1vdVY3Y4pGhPL1aqSANu8RHXr/QRL FGJeFrPLBCPPT0prTyJxmi8WzswF4Zu9vKQWGhHmfdbgDYYsvmwNEaQvGzTaCiyuoKpF f/l1eUL7IEpbBqIdI5BtwOUmojLmagITKaMsvTpi3+6JkJVEFe4/wVStfkd3Kf3B5BfP 5FlRxka5WPnOMe1H8pdchDdjGDtDS4kwcuvD8hw9zpxzxBf/4nxObTjgpjDxsgBs0CZr rjww== X-Gm-Message-State: APjAAAWCTJPzUuUoar+xJ0aftPW52n6FgAU5OkfY3Tl0i6d9rdmz1bs2 EvU0M1+SdED0jISXBElK1xJact5Eedg2v2tUHXUK7ZBM X-Google-Smtp-Source: APXvYqwj7mlTz8QAVyuKWexjbLtwLC3DK1atjlJEAW904ghO4d/9EB0C/DFajWFE/Wj3eUtKVBy4cfj59azLZvZyrOg= X-Received: by 2002:a67:80c8:: with SMTP id b191mr22942106vsd.113.1563315147252; Tue, 16 Jul 2019 15:12:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sebastian Gniazdowski Date: Wed, 17 Jul 2019 00:12:16 +0200 Message-ID: Subject: Re: zle .redisplay sometimes eating up a line To: Roman Perepelitsa Cc: Zsh Users Content-Type: text/plain; charset="UTF-8" On Mon, 15 Jul 2019 at 20:53, Sebastian Gniazdowski wrote: > > The fix is to call `zle -R` before `zle .redisplay`. > > BIG thanks! Adding zle -R before .redisplay call fixed my original > problem, and also the demonstration-sample. Turns out that, as the documentation of zle -R suggests, also replacing zle .redisplay with zle -R works. I wonder what's the difference between those two calls?