From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1003 invoked from network); 1 Aug 2000 09:20:44 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 1 Aug 2000 09:20:44 -0000 Received: (qmail 6178 invoked by alias); 1 Aug 2000 09:20:35 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12456 Received: (qmail 6156 invoked from network); 1 Aug 2000 09:20:31 -0000 Date: Tue, 01 Aug 2000 10:19:58 +0100 From: Peter Stephenson Subject: Re: Open bugs and questions? In-reply-to: "Your message of Tue, 01 Aug 2000 11:00:16 +0200." <200008010900.LAA06432@beta.informatik.hu-berlin.de> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FYL00APLWLA7C@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT Sven wrote: > Semester-holiday has definitely begun now. So, does anyone have a list > of unfixed bugs and open questions? Bart? It's a bit too open, but I'm beginning to think we need a more integrated feature control system in time for 4.0 (rather than at some unspecified future date). There's a lot more in the shell now, and people upgrading will need a better way of deciding what to keep than deciding separately which modules and which sets of shell functions they don't need. You can pretty much do it already, actually, by manipulating OMIT_MODULES, mymods.conf and FUNCTIONS_INSTALL, so possibly it can be done simply with an extra pre-configuration tool and/or some additions during the running of configure. But I think some addition is necessary, preferably with fine-grained control over the functions that go into each module (whether to include Linux functions with the completion module, for example). I would propose (just off the top of my head) the modules old completion new completion zle add ons (basic zle has to be there, but there are extra builtins/fns) zftp for completeness, all the other modules in Modules even though they are essentially just the library code. prompt themes any other identifiable sets of functions (maybe even a misc module) It might be necessary to rewrite some of the existing control mechanism to facilitate this. There are extra implications of integration, too: if the C code for a feature doesn't work, we don't want to install the functions, either. -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070