Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!oliveb!intelca!mipos3!merlyn From: merlyn@intelob.biin.com (Randal L. Schwartz @ Stonehenge) Newsgroups: comp.unix.wizards Subject: Re: Echo Summary: this is drivel, skip if you want serious stuff :-) Message-ID: <3310@mipos3.intel.com> Date: 8 Dec 88 01:23:18 GMT References: <6557@june.cs.washington.edu> <4712@mtgzz.att.com> <963@vsi.COM> <6646@june.cs.washington.edu> Sender: news@mipos3.intel.com Reply-To: merlyn@intelob.biin.com (Randal L. Schwartz @ Stonehenge) Organization: Stonehenge; netaccess via BiiN, Hillsboro, Oregon, USA Lines: 19 In-reply-to: ka@june.cs.washington.edu (Kenneth Almquist) In article <6646@june.cs.washington.edu>, ka@june (Kenneth Almquist) writes: | I've been thinking | of adding a `rename' command to allow shell builtins to be moved around. | This would allow people to say `rename test sdlkjfsdlfk' in their .profile | files to get rid of the test command in their login shells, but test would | still be around in subshells. Arrggh. But then what about my 'rename' shell script? :-) :-) :-) I think you should call your command 'xyzzy'. Or 'plugh'. Or '*'. Come to think of it, I had a shell script named '*' once. Nevermind. :-) -- Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 on contract to BiiN Technical Information Services (for now :-), in a former Intel building in Hillsboro, Oregon, USA.or ...!tektronix!inteloa[!intelob]!merlyn SOME MAILERS REQUIRE GRRRRR! Standard disclaimer: I *am* my employer!