From: Carlo Strozzi <carlos@texne.com>
To: rc@hawkwind.utcs.toronto.edu
Subject: akanga
Date: Sun, 21 Jan 2001 10:37:05 -0500 [thread overview]
Message-ID: <20010121163705.A407@polka.texne.com> (raw)
Hi all.
Foraging around the net I have found a little rc-based gem, which
name is "akanga". In spite of such an horrible name (IMO) -- I would
have called it rc+ or something like that -- this shell, which is 99%
pure rc, offers exactly those little improvements that the original
rc is lacking, the most outstanding of which are:
* read (for line-oriented input)
* mktemp
* let
* expr
* lock
Now my question: what about incorporating those features into
the main rc source code ? I sent a message to akanga's author,
mr. Wolfgang Zekoll, asking about his future plans, if any, for
akanga, but I got no reply. My concern is that if the handful of code
that implements those features does not get merged into the main rc
source, akanga will eventually get out of sync with the latter and
become obsolete. That would really be a shame.
cheers,
carlo
--
_ _ _ _ _
/ \ / \ / \ / \ / \ Contro i brevetti software
( T | e | X | n | e ) Against software patents
\_/ \_/ \_/ \_/ \_/ http://petition.eurolinux.org
reply other threads:[~2001-01-22 3:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010121163705.A407@polka.texne.com \
--to=carlos@texne.com \
--cc=rc@hawkwind.utcs.toronto.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.
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).