9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sqweek <sqweek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] what features would you like in a shell?
Date: Wed,  1 Apr 2009 10:39:17 +0800	[thread overview]
Message-ID: <140e7ec30903311939l5a793622v33c7c82d16d2eacd@mail.gmail.com> (raw)
In-Reply-To: <e542fccdca9fe8f422ee45179e05f23f@quanstro.net>

2009/4/1 erik quanstrom <quanstro@quanstro.net>:
>> I've not run into many actual problems with rc so it's pretty near
>> perfect :>
>
> pretty near.
>
> redirection has a few rough points.  dealing with a device
> that expects a write then a read like /net/dns is painful.
> i can never get the syntax right the first try.
> and (hopefully this isn't just my ignorance) i don't know how
> to open a fd to a background shell as one would in bourne.

 I haven't sat down and understood the finer points of rc's
redirection yet, but the precedence relationships between > < and |
certainly confuse the hell out of me, coming from bourne ;)

 I'd like to see a shell that, when confronted with a pipeline that
looks like "<foo ... | ... >foo", realises input and output are headed
for the same file, and does whatever it needs to do to avoid
clobbering the file before reading it.

 re not reinventing the wheel, you might want to look into the es
shell. I think this is what erik alluded to earlier - I've never used
it myself but I understand it is extremely programmable, to the point
where you can redefine the pipe operator for example.
-sqweek



  reply	other threads:[~2009-04-01  2:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 15:29 noagbodjivictor
2009-03-31 15:47 ` erik quanstrom
2009-03-31 16:10 ` matt
2009-03-31 16:26   ` erik quanstrom
2009-04-01  2:39     ` sqweek [this message]
2009-04-01  3:14       ` erik quanstrom
2009-03-31 16:14 ` rapogue
2009-03-31 16:19   ` André Günther
2009-03-31 16:19   ` erik quanstrom
2009-03-31 16:27     ` erik quanstrom
2009-03-31 16:16 ` noagbodjivictor
2009-03-31 16:47   ` erik quanstrom
2009-03-31 17:03     ` michael block
2009-04-01  9:28   ` matt
2009-04-01  9:43     ` yy
2009-04-01 10:01       ` matt
2009-04-01 12:41         ` hiro
2009-04-01 12:54           ` Martin Neubauer
2009-03-31 16:55 ` J.R. Mauro
2009-03-31 18:28 ` Corey
2009-04-02 18:41 ` John Stalker
2009-04-02 23:20   ` LiteStar numnums
2010-10-03 16:25 C H Forsyth
2010-10-05 19:12 ` erik quanstrom

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=140e7ec30903311939l5a793622v33c7c82d16d2eacd@mail.gmail.com \
    --to=sqweek@gmail.com \
    --cc=9fans@9fans.net \
    /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).