From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: How is it guaranteed that zle is active during sched call?
Date: Sun, 11 Sep 2016 00:28:39 +0200 [thread overview]
Message-ID: <CAKc7PVCGT=gwWMCx+wGaZtQMsrXa_HnLneUSmz=EZ9ZSe5RjtQ@mail.gmail.com> (raw)
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
next reply other threads:[~2016-09-10 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 22:28 Sebastian Gniazdowski [this message]
2016-09-11 18:06 ` Peter Stephenson
2016-09-11 20:08 ` Sebastian Gniazdowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKc7PVCGT=gwWMCx+wGaZtQMsrXa_HnLneUSmz=EZ9ZSe5RjtQ@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).