From: Clint Adams <clint@zsh.org>
To: zsh-workers@sunsite.dk
Subject: Re: (Fwd) RE: Archive of shell@research.att.com ?
Date: Tue, 14 Aug 2001 11:35:51 -0400 [thread overview]
Message-ID: <20010814113550.A6216@dman.com> (raw)
In-Reply-To: <1010808163943.ZM1100@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Wed, Aug 08, 2001 at 04:39:43PM +0000
> Yes, there is an archive for shell@ list available at:
I took a brief look; I'm not posting this to shell@ because I
don't have the time to follow it right now.
The adoption of bash-style /dev/{tcp,udp} into the standard
strikes me as a bad idea: not the functionality, but the
naming.
I was envisioning the use of some sort of special associative
array parameter as provided by zsh/tcp, before I was distracted.
prev parent reply other threads:[~2001-08-14 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 16:39 Bart Schaefer
2001-08-14 15:35 ` Clint Adams [this message]
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=20010814113550.A6216@dman.com \
--to=clint@zsh.org \
--cc=zsh-workers@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).