From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5448 invoked from network); 14 Jun 2001 00:43:12 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Jun 2001 00:43:12 -0000 Received: (qmail 17042 invoked by alias); 14 Jun 2001 00:42:43 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14909 Received: (qmail 17024 invoked from network); 14 Jun 2001 00:42:41 -0000 From: "Bart Schaefer" Message-Id: <010613174048.ZM27798@candle.brasslantern.com> Date: Wed, 13 Jun 2001 17:40:48 -0700 In-Reply-To: Comments: In reply to Peter Stephenson "Re: 4.0.1: menucomplete quirk leaving extra characters behind" (Jun 13, 7:48pm) References: X-Mailer: Z-Mail Lite (5.0.0 30July97) To: Peter Stephenson , zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: 4.0.1: menucomplete quirk leaving extra characters behind MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 13, 7:48pm, Peter Stephenson wrote: > Subject: Re: 4.0.1: menucomplete quirk leaving extra characters behind > > Or we can introduce a flag PM_SPECIALREADONLY which has the same > effect as PM_READONLY but can't be reset (and we complain if the user tries > to change PM_READONLY if that's set). Or we could add to struct param a mask word of those flag bits that are allowed to be changed ... but maybe that's overkill and one new flag is sufficient to cover the cases. I'd say first let's just try it with readonly being a one-way trip, and see where we end up.