zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: coloring STDERR to terminal
Date: Tue, 20 Jul 2004 14:15:07 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0407201353480.12638@toltec.zanshin.com> (raw)
In-Reply-To: <20040720151617.N326@willy_wonka>

On Tue, 20 Jul 2004, Atom 'Smasher' wrote:

> you raise some intersting issues... and not being much of a C programmer 
> myself i'm not sure how to address them... my logic is that if the 
> coloring of STDOUT, STDERR and echoing STDIN is handled ~internally~ by 
> the shell, then everything else should (FTMP) work itself out.

What you're missing is that the shell is not involved in the processing of 
these streams except insofar as it sets up the file descriptors used by 
the commands it spawns.  All the shell does or can do is start the new 
process and then get out of the way until it is finished.

The exception, in the case of zsh, is multios, where the shell explicitly 
sets up each of those file descriptors to point to a special subprocess 
that copies its single input to its multiple outputs as fast as it can.  

What you're asking for is something to copy multiple inputs to a single 
output, simultaneously adding characters (the color codes) to those inputs 
yet without mixing the result any differently than it would have been 
mixed if the writers of all those inputs had instead written directly to 
that single output.

This is, pretty much by definition, impossible, except (sometimes) at the 
level of a kernel driver.


  reply	other threads:[~2004-07-20 21:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 23:22 Atom 'Smasher'
2004-06-28  0:06 ` ari
2004-06-28  0:36   ` Atom 'Smasher'
2004-06-29 15:43 ` Bart Schaefer
2004-06-29 16:08   ` Vincent Lefevre
2004-06-29 17:14     ` Bart Schaefer
2004-06-30  7:09       ` Vincent Lefevre
2004-06-30 10:52         ` Bart Schaefer
2004-06-30 11:43           ` Vincent Lefevre
2004-06-30 12:01             ` Vincent Lefevre
2004-06-30 16:56             ` Bart Schaefer
2004-07-01 18:14               ` Vincent Lefevre
2004-07-02  0:11                 ` Bart Schaefer
2004-07-02 12:42                   ` Vincent Lefevre
2004-07-02 21:32                     ` Bart Schaefer
2004-07-20  9:10                     ` Atom 'Smasher'
2004-07-20 16:10                       ` Bart Schaefer
2004-07-20 19:27                         ` Atom 'Smasher'
2004-07-20 21:15                           ` Bart Schaefer [this message]
2004-07-20 23:30                             ` Wayne Davison
2004-07-21  3:15                               ` Bart Schaefer
2004-07-21  6:23                                 ` Wayne Davison
2004-07-21  7:30                                   ` Bart Schaefer
2004-07-21 13:19                                   ` Vincent Lefevre
2004-07-30 11:50                     ` Andy Spiegl
2004-07-30 23:44                       ` Vincent Lefevre

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=Pine.LNX.4.61.0407201353480.12638@toltec.zanshin.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /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).