zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <phil@athenaeum.demon.co.uk>
To: zsh-workers@math.gatech.edu
Subject: Re: PATCH: stat option to set hash
Date: Wed, 9 Dec 1998 18:36:06 +0000	[thread overview]
Message-ID: <19981209183606.52123@athenaeum.demon.co.uk> (raw)
In-Reply-To: <9812091016.AA43825@ibmth.df.unipi.it>; from "Peter Stephenson" on Wed 9 Dec 1998 (11:16 +0100)

Typing away merrily, Peter Stephenson produced the immortal words:
> > It seems to me
> > anomalous that stat primarily generates textual output.
> 
> There's text and there's binary and...?

It's more a case of how well it integrates into everything else.  If you
look at most of zsh's builtins and stuff, text output is used for status
stuff, job status, requesting confirmation, tabs-stuff and zle
generally.  Aside from explicit print/echo and read not much causes the
shell to produce data rather than user-fluff on stdout/err.  select
comes to mind, and pwd (which could as well be a shell wrapper around
print and $PWD).  User-fluff includes whence and internal status
reporting stuff.

Normally zsh acts as a filter controller, not a data-source beyond basic
user-input stuff.  I know I'm not important in zsh development, but it
just feels wrong when I see stat shove stuff to stdout.

I know, I'm not expressing this very well.  It's just... feel.
-- 
--> Phil Pennock ; GAT d- s+:+ a22 C++(++++) UL++++/I+++/S+++/H+ P++@ L+++
E-@ W(+) N>++ o !K w--- O>+ M V !PS PE Y+ PGP+ t-- 5++ X+ R !tv b++>+++ DI+ D+
G+ e+ h* r y?


  reply	other threads:[~1998-12-09 19:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-09  1:11 Phil Pennock
1998-12-09 10:16 ` Peter Stephenson
1998-12-09 18:36   ` Phil Pennock [this message]
1998-12-10  8:48     ` Peter Stephenson

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=19981209183606.52123@athenaeum.demon.co.uk \
    --to=phil@athenaeum.demon.co.uk \
    --cc=zsh-workers@math.gatech.edu \
    /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).