delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_PD,TW_RX |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <4ECD5818.4040809@gmail.com> |
Date: | Wed, 23 Nov 2011 20:31:20 +0000 |
From: | Dave Kilroy <kilroyd AT googlemail DOT com> |
User-Agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 |
MIME-Version: | 1.0 |
To: | Ronald Fischer <ynnor AT mm DOT st> |
CC: | cygwin AT cygwin DOT com |
Subject: | Re: chere, mksh and pdksh |
References: | <1321987312 DOT 4604 DOT ezmlm AT cygwin DOT com> <1322035933 DOT 21972 DOT 140661002574293 AT webmail DOT messagingengine DOT com> |
In-Reply-To: | <1322035933.21972.140661002574293@webmail.messagingengine.com> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On 23/11/2011 08:12, Ronald Fischer wrote: >> 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? If I recall, this was to make it simple to locate any entry chere may have created. > 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. I think it would have to be a munged path. I suspect '/' would not be valid in a key name. New shells would depend on the shell conforming to some minimal requirements. If I recall, the existing shells do login shells slightly different. > 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). My feeling is that most people have a prefered terminal, but may need to use different shells. To do what you want, my feeling is that it's easier use what chere does as an example. You can even script it with something like: chere -ip -t mintty -s ksh | sed -e "s/cygwin_ksh/mintty_ksh/g" > a.sh chere -ip -t rxvt -s ksh | sed -e "s/cygwin_ksh/rxvt_ksh/g" > b.sh ./a.sh ./b.sh Dave. -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |