From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-users@zsh.org
Subject: Re: print to the terminal in zle
Date: Sat, 27 Jul 2013 17:30:55 +0100 [thread overview]
Message-ID: <20130727163055.GB14201@chaz.gmail.com> (raw)
In-Reply-To: <20130726203931.3e05f151@pws-pc.ntlworld.com>
2013-07-26 20:39:31 +0100, Peter Stephenson:
> On Fri, 26 Jul 2013 14:48:11 +0100
> Stephane Chazelas <stephane.chazelas@gmail.com> wrote:
> > recently, Debian broke some of my scripts using ZLE in `zsh -i` by adding:
> >
> > function zle-line-init () {
> > emulate -L zsh
> > printf '%s' ${terminfo[smkx]}
> > }
> >
> > To /etc/zsh/zshrc
> >
> > That smkx escape sequence is printed to stdout instead of the terminal.
>
> It's just occurred to me that maybe zle special functions should be run
> with stdout and stdin set explicitly to the terminal. Arguably they
> have no business knowing about a redirected stdout or stdin since they
> run in a context where that's meaningless. stderr would be good enough
> for debugging.
[...]
In my script (http://www.zsh.org/mla/users/2007/msg01187.html),
I need to be able to access stdout from a zle function, though I
could change it to use another fd (my modified "accept-line"
writes the $BUFFER to stdout that goes to a pipe) (and yes,
there was a reason to write it in such a convoluted way, but
that was years ago)
Given that ZLE can be used from "vared" to implement a line
editor for something else than the shell prompt, where a system
of functions can be defined by the user, it feels wrong to hide
stdout from those functions.
Think of
vared var | {
some processing that interacts with what widgets write to
stdout
}
Now, I agree it's a clean way to expose the terminal to the ZLE
widgets would they need to send/recv data to/from it, and one
can dup to another fd if they need to access the original
stdin/out.
vared var 3>&1 | ...
or use a coproc...
--
Stephane
next prev parent reply other threads:[~2013-07-27 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 13:48 Stephane Chazelas
2013-07-26 17:05 ` Peter Stephenson
2013-07-26 17:36 ` Frank Terbeck
2013-07-27 16:20 ` Stephane Chazelas
2013-07-27 18:58 ` Greg Klanderman
2013-07-26 19:39 ` Peter Stephenson
2013-07-27 0:00 ` Bart Schaefer
2013-07-27 16:30 ` Stephane Chazelas [this message]
2013-07-27 17:02 ` Stephane Chazelas
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=20130727163055.GB14201@chaz.gmail.com \
--to=stephane.chazelas@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).