From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1961 invoked from network); 4 Apr 2000 13:32:48 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 4 Apr 2000 13:32:48 -0000 Received: (qmail 27007 invoked by alias); 4 Apr 2000 13:32:35 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10466 Received: (qmail 26993 invoked from network); 4 Apr 2000 13:32:34 -0000 Date: Tue, 4 Apr 2000 15:32:30 +0200 (MET DST) Message-Id: <200004041332.PAA14140@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk Subject: Style names >>From Peter's compinstall: # TODO: I couldn't be bothered to handle sort because it does different # things in different context (which I'm kind of against anyway). As far as I can see, there are currently four styles used in more than one type of context: - cursor: paths and predict, different possible values - list: i-c-w and history, but means almost the same in both - sort: history, files, _expand, different possible values, slightly different meaning - stop: history and i-c-w, completely different meaning So, should we change that to: - use ambiguous (or first-ambiguous?) for paths - leave the list style as it is - use file-sort (or sort-files; I'm thinking about file-patterns) for files, leave the rest - stop-keys for i-c-w (and change break to break-keys) Or use better names? (;-) Or make more dramatic changes? Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de