From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1446 invoked from network); 14 Jun 1999 14:51:21 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Jun 1999 14:51:21 -0000 Received: (qmail 1817 invoked by alias); 14 Jun 1999 14:40:42 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6619 Received: (qmail 1790 invoked from network); 14 Jun 1999 14:40:40 -0000 Date: Mon, 14 Jun 1999 15:12:24 +0200 (MET DST) Message-Id: <199906141312.PAA23929@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Peter Stephenson's message of Mon, 14 Jun 1999 09:15:47 +0200 Subject: Re: WORDCHARS, etc. Peter Stephenson wrote: > One problem remains with the $NUMERIC mechanism: there's no way of > differentiating between the case where the prefix was given as 1 and where > no prefix was given. This is already noticeable in the completion code for > specifying numbers of correction. Possibilities are either a separate > parameter, which is clumsy, or altering NUMERIC in some way: I would > prefer that it is still numerically 1 in either case to avoid confusing > functions, but maybe it could be '+1' if the prefix wasn't set. That would > mean making it a string instead of an integer parameter. I wouldn't like it to be such a string because we can't easily get at the default value then. How about leaving it unset if no numeric argument is given? To be able to say ${NUMERIC:-1}. (I had this idea some time ago but then forgot to ask...) Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de