Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: esh
- To: tlug@example.com
- Subject: Re: esh
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Date: Fri, 1 Sep 2000 19:14:07 +0900 (JST)
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <20000901173100.C26194@example.com>
- References: <20000831170206.A23277@example.com><20000831205835.A13688@example.com><20000901173100.C26194@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <lGGIFD.A.toD.QP4r5@example.com>
- Resent-Sender: tlug-request@example.com
>>>>> "FB" == Frank BENNETT <bennett@example.com> writes: FB> I spent a couple of days with esh, worked up a script that did FB> what I needed, and then discovered that: Why esh? While I don't have any glandular incompatibility with Lisp (admittedly I haven't done `chsh /usr/bin/xemacs' in quite a while, and certainly not enough of a bigot to do `ln -s /usr/bin/xemacs /bin/sh' ;-) esh look like a pure exercise in namespace pollution. Is there more to it than that? -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."
- Follow-Ups:
- Re: esh
- From: Simon Cozens <simon@example.com>
- References:
- Re: esh
- From: Frank BENNETT <bennett@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: esh
- Next by Date: Re: esh
- Prev by thread: Re: esh
- Next by thread: Re: esh
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links