9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: George Michaelson <ggm@apnic.net>
To: 9fans@cse.psu.edu
Cc: r@geekmail.cc
Subject: Re: [9fans] v8 shell
Date: Thu, 13 Nov 2003 23:44:00 +0000	[thread overview]
Message-ID: <20031113234400.7e61f87b.ggm@apnic.net> (raw)
In-Reply-To: <e004e732ced8e1653a716c793de55e43@google.com>


>
> for example, the 'builtin' trick in modern shells comes out of the v8
> shell but the other half is missing.
>
> korn shell or bash:
>
> 	$ type cd
> 	cd is a shell builtin
> 	$
>
> v8 shell:
>
> 	$ whatis cd
> 	builtin cd
> 	$
>
> see the difference? the latter is executable code.  why was it important
> to `fix' this in the committee?  bitterness rules.

I found I had to set the PS1 and PS2 to be known shell comment markers to get
things work work sanely when I played with this in shell a while back, and even
then it wasn't very good. Its unfortunate that the $ is also a leadin to
variable expansion, if it was functionally more like ; or :; it would have made
it easier to snarf entire sequences of commands from screens.

>
> maybe that's why rc happened.  probably was a factor.  i know i asked
> td to design rc, but i also did the work in creating the v8 shell. i
> don't really remember.
>
> -rob

like many people, I haven't been able to face the terminal moraine of rc, to get
to the mountain tops behind it. If only there was a budget for clue, and a
market for selling it in this area.

-George


--
George Michaelson       |  APNIC
Email: ggm@apnic.net    |  PO Box 2131 Milton QLD 4064
Phone: +61 7 3367 0490  |  Australia
  Fax: +61 7 3367 0482  |  http://www.apnic.net


  reply	other threads:[~2003-11-13 23:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.21.0311131606190.27715-100000@zenon.ceid.upatras.gr>
2003-11-13 16:06 ` Taj Khattra
2003-11-13 17:41   ` rob pike, esq.
2003-11-13 23:44     ` George Michaelson [this message]
2003-11-14  0:43       ` rog
2003-11-14  6:59         ` boyd, rounin
2003-11-17 10:26           ` Douglas A. Gwyn
2003-11-17 12:13             ` Charles Forsyth
2003-11-18  9:48               ` Douglas A. Gwyn
2003-11-14 12:04         ` John Murdie
2003-11-14 18:01           ` rog
2003-11-14 19:04             ` boyd, rounin
2003-11-14 19:18               ` rog
2003-11-14 19:31                 ` boyd, rounin
2003-11-14 22:25             ` Roman Shaposhnick
2003-11-16 11:45             ` Richard Miller
2003-11-16 12:01               ` Geoff Collyer
2003-11-16 12:21                 ` Richard Miller
2003-11-17 20:31                   ` rog
2003-11-16 14:23               ` Russ Cox
2003-11-16 14:35                 ` Richard Miller
2003-11-15 15:03           ` a
     [not found] ` <oprykztjlztsux9g@smtp.borf.com>
2003-11-14  0:41   ` boyd, rounin
2003-11-14 17:51     ` rog
2003-11-14 18:51       ` boyd, rounin
2003-11-17 10:26       ` Douglas A. Gwyn
2003-11-14  7:05   ` boyd, rounin
2003-11-14  8:13 boyd, rounin
2003-11-14 18:12 Richard C Bilson
2003-11-14 19:09 ` rog
2003-11-14 19:12 ` boyd, rounin

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=20031113234400.7e61f87b.ggm@apnic.net \
    --to=ggm@apnic.net \
    --cc=9fans@cse.psu.edu \
    --cc=r@geekmail.cc \
    /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).