From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Could multios response positively to isatty(1) test?
Date: Thu, 7 Feb 2019 17:46:38 +0100 [thread overview]
Message-ID: <CAKc7PVBfyC+9wg=WRn-rxhGHkow7f-e+fyvpYTCOfEH+LuY=dQ@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVDYtms1L85GvNufswZ7zm1DFxWUwhHXvP_CEhkPT==9LQ@mail.gmail.com>
On Thu, 7 Feb 2019 at 17:41, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
> Implementing isn;'t necessary – what's needed is the knowledge, that
> original fd=1 is a tty,, and conveying that lfurther to the zsh
> process realizing the multios – i.e.: conveying only the test answer
> to isatty(fd=1), not the terminal implementation. Simple forwarding of
> all data to the terminal through non-terminal. works (a good test: vim
> | cat).
No, that's isn't logical, correct statement. The correct one:
What's needed is the knowledge, that some (one) of mutlios targets is
a tty, and conveying that information upper to the multios-process, so
that it can mark (?) it's exposed to the writer (the application that
needs a terminal) pipe or FD (unsure)
Confirming test: vim | cat works without any problems, so the exposed
to the application pipe or FD doesn't have to implement a terminal.
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next prev parent reply other threads:[~2019-02-07 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190207132020epcas2p21907126ab733665c20d5881eb13488ef@epcas2p2.samsung.com>
2019-02-07 13:18 ` Sebastian Gniazdowski
2019-02-07 15:02 ` Peter Stephenson
2019-02-07 16:41 ` Sebastian Gniazdowski
2019-02-07 16:46 ` Sebastian Gniazdowski [this message]
2019-02-07 16:50 ` Peter Stephenson
2019-02-07 17:55 ` Sebastian Gniazdowski
2019-02-07 18:56 ` Philippe Troin
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='CAKc7PVBfyC+9wg=WRn-rxhGHkow7f-e+fyvpYTCOfEH+LuY=dQ@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=p.stephenson@samsung.com \
--cc=zsh-workers@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).