zsh-users
 help / color / mirror / code / Atom feed
From: Atom 'Smasher' <atom@suspicious.org>
To: zsh-users@sunsite.dk
Subject: Re: coloring STDERR to terminal
Date: Tue, 20 Jul 2004 05:10:40 -0400 (EDT)	[thread overview]
Message-ID: <20040720045514.V326@willy_wonka> (raw)
In-Reply-To: <20040702124259.GS2033@ay.vinc17.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

as i suspected, there doesn't seem to be a really good way to do this... 
although there are several ways to ~almost~ do it well.

that said, i'd like to request a feature for coloring STDERR. i think the 
best way to do it would be an environment variable, something like this:
 	STDERR_COL=91,107

which would wrap STDERR in:
 	^[[91m^[[107m{output}^[[0m

maybe a STDIN_COL and STDOUT_COL could also be handy?

that seems to be the only way to ~properly~ deal with the synchronization 
and buffer issues.


  	...atom

  _________________________________________
  PGP key - http://atom.smasher.org/pgp.txt
  762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
  -------------------------------------------------

 	"Do not wait; the time will never be 'just right.'
 	 Start where you stand, and work with whatever
 	 tools you may have at your command, and better
 	 tools will be found as you go along."
 		-- Napoleon Hill
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.6 (FreeBSD)
Comment: What is this gibberish?
Comment: http://atom.smasher.org/links/#digital_signatures

iQEcBAEBCAAGBQJA/OGWAAoJEAx/d+cTpVcizhYH/2gi5w9cjys16gr3+49wUdoE
llxeoAIBoyjd/MrZE7OLniL5OYrYgPjuus5SpoXoO5x4UY7azVWbLggIEVQGs0+9
Jyl8aJvhpIFTTTKqCVoUTgdbBPXbA57OWQ63FSqmPS8c3kRifi8NF3oHqHXVk2hu
/mUJJx6ROxWcf2S3LArOmzHxpAo+f4sASL8MRoGmrl46n38isYh4VAr61Tino5yu
OsnAnkOdgSqreXLP10LwRYnd84khn1tDZVqY+6CeEW3W7of/8sNxp6qDhO6tttFA
uPMvcY5COXZbsiGRR8LjHaWrGrpVLqU0h3zkT5H2rXenxsyMF5VffRtprfDJ2pk=
=8KIU
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2004-07-20  9:13 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' [this message]
2004-07-20 16:10                       ` Bart Schaefer
2004-07-20 19:27                         ` Atom 'Smasher'
2004-07-20 21:15                           ` Bart Schaefer
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=20040720045514.V326@willy_wonka \
    --to=atom@suspicious.org \
    --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).