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:41:21 +0100 [thread overview]
Message-ID: <CAKc7PVDYtms1L85GvNufswZ7zm1DFxWUwhHXvP_CEhkPT==9LQ@mail.gmail.com> (raw)
In-Reply-To: <1549551768.5863.1.camel@samsung.com>
On Thu, 7 Feb 2019 at 16:10, Peter Stephenson <p.stephenson@samsung.com> wrote:
>
> On Thu, 2019-02-07 at 14:18 +0100, Sebastian Gniazdowski wrote:
> > Hello,
> > If at least one of the outputs of the multios-utilizing invocation is
> > to a terminal, .e.g
> >
> > print "$fg[blue]A TEST$reset_color" \
> > > >(ansifilter >>! "log.txt") 1> >/dev/tty
> >
> > then could Zshell answer positively to the isatty(1) test for the
> > application (like e.g. vim) placed the way that the print-command is?
> > Is this doable?
>
> The short answer's no. Implementing pty support in the core shell would
> be a bug-prone maintenance disaster.
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).
I wonder what the test (isatty(1)) does. Does it invoke some ioctl()
that somehow reaches the zsh multios-process.. No rather not, but what
then? Maybe some flag on the fd: that is visible to the
application/writer?
> You're best bet is some kind of pty wrapper (as already discussed) plus
> something looking a bit like tee. This is not stuff you want within zsh
> (unless as an add-on --- but zpty is bad enough to maintain, so I wouldn't
> recommend even that).
>
> pws
>
--
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:41 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 [this message]
2019-02-07 16:46 ` Sebastian Gniazdowski
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='CAKc7PVDYtms1L85GvNufswZ7zm1DFxWUwhHXvP_CEhkPT==9LQ@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).