From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19477 invoked from network); 2 May 2001 07:57:36 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 May 2001 07:57:36 -0000 Received: (qmail 9560 invoked by alias); 2 May 2001 07:57:31 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14196 Received: (qmail 9548 invoked from network); 2 May 2001 07:57:31 -0000 From: "Bart Schaefer" Message-Id: <1010502075717.ZM7710@candle.brasslantern.com> Date: Wed, 2 May 2001 07:57:17 +0000 In-Reply-To: <15087.39833.240011.861487@starf.org> Comments: In reply to "F. G. Marx" "_use_lo is still being refered to" (May 2, 1:31am) References: <1010501150227.ZM6942@candle.brasslantern.com> <15087.39833.240011.861487@starf.org> X-Mailer: Z-Mail (5.0.0 30July97) To: fmarx@crosswinds.net, zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: _use_lo is still being refered to MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 2, 1:31am, F. G. Marx wrote: } } Any posibility it's in shared memory (I run three vt's + X(-terms)) (and I } test (and update zcompdump) in one vt while the old version runs in the } others). No, it can't be shared memory. Have you tried `ls -l $^fpath/_use_lo' ? If all else fails, put `exec 2> /tmp/xtrace; set -x' very early in your init files, and then look through the xtrace output for _use_lo. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net