git: fqa.9front.org

--- a/fqa8.ms

+++ b/fqa8.ms

@@ -35,8 +35,6 @@

 .FG using9front jpg

-.FG rails jpg

 When applied consistently, simple conventions can combine to provide powerful results. In Plan 9,

 .I conventions

 are preferred to

@@ -62,13 +60,17 @@

.DE

 .html - <br />

-The

-.CW rc

-shell was written by

+Later,

+.ihtml a <a href="https://marc.info/?l=9fans&m=111558921626149">

+Rob Pike

+.ihtml a

+asked

 .ihtml a <a href="http://en.wikipedia.org/wiki/Tom_Duff">

 Tom Duff

 .ihtml a

-for

+to design the

+.CW rc

+shell for

 .ihtml a <a href="https://web.archive.org/web/20170601063844/http://www.cs.bell-labs.com/10thEdMan">

 Research UNIX v10.

 .ihtml a

@@ -91,6 +93,44 @@

 .ihtml a <a href="http://man.9front.org/1/rc">

 .CW rc(1)

 .ihtml a

+.P1

+Subject:    Re: [9fans] v8 shell

+From:       "rob pike, esq."

+Date:       2003-11-13 17:41:24

+i fought fairly hard to get the key features of the v8 shell adopted

+into posix.  these included exportable functions and output from

+commands like whatis that could be read as input.  but i didn't fight

+hard enough because i didn't fight at every single committee meeting.

+as soon as i stopped going, the changes were reverted ("thank god he's

+gone").  the experience soured me for life on contributing to

+standards committees.

+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.

+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

+.P2

 .html - <a name="8.1.1" />

 .ihtml h3 <h3>

--

⑨