Message-Id: <1322035933.21972.140661002574293@webmail.messagingengine.com>
From: "Ronald Fischer" <ynnor@mm.st>
To: cygwin@cygwin.com
Cc: kilroyd@googlemail.com
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <1321987312.4604.ezmlm@cygwin.com>
References: <1321987312.4604.ezmlm@cygwin.com>
Subject: Re: chere, mksh and pdksh
Date: Wed, 23 Nov 2011 09:12:13 +0100
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

> It's been a while since I last refreshed the package, so I'll have a 
> look and see if I can get something done ASAP.

Is there a technical reason, why chere needs to know a predefined set of
"keys" for the shell to install? For instance, would it not be
sufficient to pass the path to the shell? In this case, new shells can
be installed without the need to update chere. Also, if I can use the
path to the shell as a "key", I could (by using appropriate symlinks)
have several "chere" entries for the same shell (for instance, mintty
with ksh AND rxvt with ksh).

Ronald
-- 
Ronald Fischer <ronaldf@eml.cc>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple