From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-21862-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 25371 invoked by alias); 10 Sep 2016 22:29:08 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 21862
Received: (qmail 16969 invoked from network); 10 Sep 2016 22:29:08 -0000
X-Qmail-Scanner-Diagnostics: from mail-qk0-f176.google.com by f.primenet.com.au (envelope-from <sgniazdowski@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.220.176):SA:0(0.0/5.0):. 
 Processed in 0.315408 secs); 10 Sep 2016 22:29:08 -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.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS,
	T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1
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.220.176 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=eG8+vmRbI04LE4GXhgJ2Soe2oooeWj4F5JPHiiPYZEQ=;
        b=pv852tmoK3CwmI+WpQ5tzEI+hNTFcKmflm/sq3LoEk8uUgP0quQvAibu7uxxhtc44A
         my+T1TMEMjbx5qM2Ks/L8fO7FKon0WLnw1gM7P/+RKuZauzvGc+DJeMKk/Z8xQ0Kbb6W
         +6U5Dr+x01pgHu+ikmHTCqHvh18/YaDfODuZUNx8wp125QWDBG77THZBpP5AyAOQTML0
         mzpz/Lw5LFEUZZwinENItWDhnUXPkKBsCG9On5sGkfJrgbIB1W7XAldxKMJZAWXiHpod
         zkfo0IeBUocqwc40x2ga22LzvD6jpnUg8djop0efTQ3525s2LDiMAxUg1rdjCNRUvw/o
         W+dw==
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=eG8+vmRbI04LE4GXhgJ2Soe2oooeWj4F5JPHiiPYZEQ=;
        b=NNBGWmwpwt+Kz84ySS703K6eennV/EcET5hBpKd5lBW/rDm7oVlQIzGF5KuLqVhQ9W
         RwjvxkeSxdymRvx7ygqYhJrRYvfLCNHm81e7xqo180bPiwVl90eeyFc7WuFMe4wg9d38
         u51xtPjMOZ1Qgge5MlWyMD1eCHvfSEvCOXqLy3VDmpKY5HIk0y5+bmzw7YS9jw7wUuCt
         AYBX+6W+lm4gykKnTgAh+yeKU1dyopL5tmamWcyHlTfEYV0UBwxV1oqDTsPtT/xp9qMf
         bfKvjP6nhFdBArl6zLZqWVRk4Ep5kaGtXcMjO6owyDKojEX/C+a7gtTCLfzhSW4ykP+g
         2i1A==
X-Gm-Message-State: AE9vXwMekPlGUb6ZIoTtCvsjMgz0WsdelzY0aT2/MBO0u7C826VmqCOrUgegbSupcJpM7btdVZhRVpLrwGUDPg==
X-Received: by 10.55.169.193 with SMTP id s184mr12008389qke.3.1473546539807;
 Sat, 10 Sep 2016 15:28:59 -0700 (PDT)
MIME-Version: 1.0
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Sun, 11 Sep 2016 00:28:39 +0200
Message-ID: <CAKc7PVCGT=gwWMCx+wGaZtQMsrXa_HnLneUSmz=EZ9ZSe5RjtQ@mail.gmail.com>
Subject: How is it guaranteed that zle is active during sched call?
To: Zsh Users <zsh-users@zsh.org>
Content-Type: text/plain; charset=UTF-8

Hello,
I saw codes on the internet that advise doing "zle && zle
reset-prompt" when wanting a Zle change from a sched call, e.g. here (on
the bottom, last 11 item):

http://chneukirchen.org/blog/archive/2013/03/10-fresh-zsh-tricks-you-may-not-know.html

I once too occurred sched calls that indeed were zle == false, and
added such "zle &&" guard too. Now when I test I always get zle
active. When to expect lack of zle, can this be predicted? Will
re-scheduling (with +1 second) help?

Best regards,
Sebastian Gniazdowski