Date: Thu, 24 Feb 2011 17:26:44 -0700 From: Chad Perrin <perrin@apotheon.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Backtick versus $() Message-ID: <20110225002644.GA14159@guilt.hydra> In-Reply-To: <AANLkTik0r5skC0vn0OAGX1_MQDMdsrTK3943iF_rwNzD@mail.gmail.com> References: <AANLkTik88V5Bb2BWM0Kpv3rWfek9_%2BgjqmEt6UbsVjpS@mail.gmail.com> <loom.20110224T220407-811@post.gmane.org> <AANLkTikAB--0Hrw76cbdzgfmeJMPt_N7isaw%2Byn_-QMn@mail.gmail.com> <20110224234044.0df661c1.freebsd@edvax.de> <20110224225425.GB13490@guilt.hydra> <20110225001301.e4f6d95f.freebsd@edvax.de> <21929_1298589484_4D66E72C_21929_309_1_D9B37353831173459FDAA836D3B43499BD35499F@WADPMBXV0.waddell.com> <AANLkTinu1KB=Lz7rsH5TiZXHr61gH8AWFP=quJ9=8iJH@mail.gmail.com> <20110224232404.GA13838@guilt.hydra> <AANLkTik0r5skC0vn0OAGX1_MQDMdsrTK3943iF_rwNzD@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'll try to help make it easy for you, since you seem to be having a lot of trouble grasping the concept of actually trying to make a point via logical argument and presentation of evidence: Start with the Wikipedia page comparing command shells [0]. Look through the various tables there -- feel free to ignore the "Programming features" table since it's irrelevant to the question of what makes a good interactive user shell -- to see where shells differ. Based on the differences you find, build up a list of reasons that tcsh is not as good a choice as mksh. Next, offer some examples of common command line syntax rules and how they affect the way we compose commands. Such examples should include stuff like: * environment variable assignment, printing, and export * nesting commands * completion and history access * useful configuration file characteristics and capabilities Then, of course, you can go on to further strengthen your case with references to dependencies, licensing, resource consumption and on-drive size, bugs, and so on. Any of this stuff might actually present a meaningful argument, as opposed to just asserting other people are idiots, claiming you're right with nothing to back it up, and generally waving your hands and making a lot of noise without convincing anyone of anything. (By the way, I'll save you the trouble of referring to the license. I know that mksh uses the same license as the MirOS project, which is a variant of the Historic Permission license. It's a copyfree license; I have no objects to using it on those grounds, personally.) --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk1m90QACgkQ9mn/Pj01uKUtXQCgyjfOANsK68jawnkXx/MkQkK6 5Q0AoPR9DyLsIJ/Hkf4ElMqenc95jBXg =Ibfd -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110225002644.GA14159>