zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: How is it guaranteed that zle is active during sched call?
Date: Sun, 11 Sep 2016 22:08:22 +0200	[thread overview]
Message-ID: <CAKc7PVDB_JkdwAkWxTBqK_9Twe1=bpNMYnBeGX9VPZSyjOY4kg@mail.gmail.com> (raw)
In-Reply-To: <20160911190648.1f36251a@ntlworld.com>

On 11 September 2016 at 20:06, Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
> It's not guaranteed that zle will be active during a sched call.
> Sched is generally handled as part of the pre-prompt functions; there is
> no intended linkage between this and zle.  Any interaction is not
> thought out (to my knowledge --- and sched is an old function that
> hasn't been tinkered with for a long time, I think).

That for a moment sounded scary as if sched wouldn't be considered
important. I just finished initial version of a Zconvey plugin. It
integrates multiple Zsh sessions and will serve as a base for other
plugin that will make all this semi-graphical. I use sched to pull a
flock-guarded text file, to see if there are commands to run. You said
Zle isn't thought to be working with Sched but the miraculous ioctl(
0, TIOCSTI, c ); saved me totally, everything works, I can update
command line from Sched:

https://asciinema.org/a/ayklrum7g4ut2hpt7mg6j0nzj

Maybe Sched could be revisited a little and pulled up to work with
Zle, .kill-buffer at least?

Best regards,
Sebastian Gniazdowski


      reply	other threads:[~2016-09-11 20:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-10 22:28 Sebastian Gniazdowski
2016-09-11 18:06 ` Peter Stephenson
2016-09-11 20:08   ` Sebastian Gniazdowski [this message]

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='CAKc7PVDB_JkdwAkWxTBqK_9Twe1=bpNMYnBeGX9VPZSyjOY4kg@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=p.w.stephenson@ntlworld.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).