From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11739 invoked from network); 13 Apr 2000 15:56:05 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Apr 2000 15:56:05 -0000 Received: (qmail 6278 invoked by alias); 13 Apr 2000 15:55:48 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10742 Received: (qmail 6188 invoked from network); 13 Apr 2000 15:55:37 -0000 From: "Bart Schaefer" Message-Id: <1000413155523.ZM17016@candle.brasslantern.com> Date: Thu, 13 Apr 2000 15:55:23 +0000 In-Reply-To: <200004131246.OAA14948@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: List of unresolved issues" (Apr 13, 2:46pm) References: <200004131246.OAA14948@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: List of unresolved issues MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 13, 2:46pm, Sven Wischnowsky wrote: } Subject: Re: List of unresolved issues } } } Bart Schaefer wrote: } } > Some of these may actually have been resolved and I just forgot/missed it. } > Also, these are only issues raised in messages I sent myself. } > } > ... } > 10187 combining multiple zstyle commands into one } } I offer to write it when you folks decide that we want it. Actually, I now think the shell function implementation is fine. Maybe just copy that function into Functions/Misc? I don't care about the -L output part. } > 10071 xtrace behavior of `.' and `source' } } I still find our behaviour much more consistent and it gives us both } possibilities. So if at all, I think we should use a option for it } (yet another `emulate ksh' thing). I, too, think it should stay as it is, but I didn't want the decision to be made by simply being overlooked. } > 9778 hanging on loops with lots of output } } Oops. I had forgotten about this one. Does it still happen? At last report it did, but then I've never been able to reproduce it myself. } > ... } > 9062 suspending `.' / `source' } } An option? Tested only after the init scripts have been read? Again, I don't care, this could stay the way it is. It's another bash/ksh thing though, IIRC. } > 8698 bad node type in freenode (related to 9095?) } } I sent a patch for this in 8721 (at least it solved it for me). OK, that's fine; as I said, I may have missed the solutions to some of these. } And there is also still your FPATH-in-the-environment-and-then-that-if } thing... Yes, I was intending to look at that myself. However, I'm about to go out of town for a week (starting tomorrow (i.e. Friday) morning) so if somebody else has a chance to examine it, please go ahead. I may answer some more mail tomorrow before heading out, but there's not even a telephone where I'll be next week, so past tomorrow you won't hear from me until after Easter. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com