From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2428 invoked from network); 8 Nov 2005 18:44:34 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 8 Nov 2005 18:44:34 -0000 Received: (qmail 51297 invoked from network); 8 Nov 2005 18:44:25 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 8 Nov 2005 18:44:25 -0000 Received: (qmail 17389 invoked by alias); 8 Nov 2005 18:44:19 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9670 Received: (qmail 17380 invoked from network); 8 Nov 2005 18:44:18 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 8 Nov 2005 18:44:18 -0000 Received: (qmail 50370 invoked from network); 8 Nov 2005 18:44:18 -0000 Received: from dsl3-63-249-88-2.cruzio.com (HELO dot.blorf.net) (63.249.88.2) by a.mx.sunsite.dk with SMTP; 8 Nov 2005 18:44:18 -0000 Received: by dot.blorf.net (Postfix, from userid 1000) id B4D588EDE; Tue, 8 Nov 2005 10:44:16 -0800 (PST) Date: Tue, 8 Nov 2005 10:44:16 -0800 From: Wayne Davison To: Sebastian Stein Cc: zsh-users@sunsite.dk Subject: Re: Is zsh buggy in connection with screen? Message-ID: <20051108184416.GL24349@dot.blorf.net> References: <20051108130233.GA6146@hpfsc.de> <20051108141317.GQ27583@ay.vinc17.org> <20051108174411.GH24349@dot.blorf.net> <20051108180528.GJ24349@dot.blorf.net> <20051108181629.GA6125@hpfsc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051108181629.GA6125@hpfsc.de> User-Agent: Mutt/1.5.9i X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.4 On Tue, Nov 08, 2005 at 07:16:29PM +0100, Sebastian Stein wrote: > Yeah, from time to time still vim gets killed. Any ideas? Are there > other variables, which must be saved? If you're leaving a vim running, it won't get told about the new environment values until its next invocation from the shell, so there may not be anything we can do to prevent it from dying. You said that bash does not exhibit this problem? If it's not just pure chance that prevented prior bash-related failures, you might want to dump the full set of environment variables from bash-inside-screen and zsh-inside-screen and look for differences -- perhaps if vim starts up with some different environment info it behaves differently (that doesn't seem likely, but it's a possibility)? ..wayne..