From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <50204b4f64941301a658e83f9bf6d1be@coraid.com> References: <773C7824-C50D-49EE-9CF8-74E91515F2F3@corpus-callosum.com> <201011051807.53647.dexen.devries@gmail.com> <201011051832.14379.dexen.devries@gmail.com> <50204b4f64941301a658e83f9bf6d1be@coraid.com> Date: Fri, 5 Nov 2010 18:37:04 +0000 Message-ID: From: roger peppe To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Plan9 development Topicbox-Message-UUID: 78341956-ead6-11e9-9d60-3106f5b1d025 On 5 November 2010 18:14, erik quanstrom wrote: >> > -- and then traversing it in a sensible order. How's that for daily us= e >> > shell? >> > >> > >> Why is a shell that can generate acyclic digraphs of dependencies bad? >> =C2=A0Someone clearly found a use for it at some point or it wouldn't ha= ve been >> done. > > it is silly bloat if it's not an essential part of the shell. > but (as andrey has noted) =C2=A0if you were to replace the > machinery behind these normal shell dag builders > ('&', '&&', '||', if, '|', 'and '`{}') with something general > enough to replace mk, you'd be on to something. i did a mash-inspired version of mk as an inferno shell module once. it required no new syntax (although it could be confused by files named ":"...) part of the problem was that it's not that useful to have a "mkfile"-like syntax that's only understood on one system. we ended up porting mk.