From owner-freebsd-current@FreeBSD.ORG Tue Jul 15 02:07:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB1BA37B401; Tue, 15 Jul 2003 02:07:31 -0700 (PDT) Received: from phys9911.phys.tue.nl (PHYS9911.phys.tue.nl [131.155.108.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B70143FCB; Tue, 15 Jul 2003 02:07:30 -0700 (PDT) (envelope-from karelj@phys9911.phys.tue.nl) Received: from phys9911.phys.tue.nl (localhost [127.0.0.1]) by phys9911.phys.tue.nl (8.12.9/8.12.9) with ESMTP id h6F97eJR080164; Tue, 15 Jul 2003 11:07:40 +0200 (CEST) (envelope-from karelj@phys9911.phys.tue.nl) Received: (from karelj@localhost) by phys9911.phys.tue.nl (8.12.9/8.12.9/Submit) id h6F97e9p080163; Tue, 15 Jul 2003 11:07:40 +0200 (CEST) Date: Tue, 15 Jul 2003 11:07:40 +0200 From: "Karel J. Bosschaart" To: Andreas Klemm Message-ID: <20030715090740.GA77879@phys9911.phys.tue.nl> References: <200307142038.h6EKciQ06885@mailgate5.cinetic.de> <20030714204643.GA14890@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030714204643.GA14890@titan.klemm.apsfilter.org> User-Agent: Mutt/1.4.1i cc: Thorsten Greiner cc: current@freebsd.org Subject: Re: Vim: Caught deadly signal BUS (after -current update with new gcc) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 09:07:32 -0000 On Mon, Jul 14, 2003 at 10:46:43PM +0200, Andreas Klemm wrote: > On Mon, Jul 14, 2003 at 10:38:44PM +0200, Thorsten Greiner wrote: > > > > You can work around this by unsetting SESSION_MANAGER in your > > > > environment. I have no idea what the root cause is... > > > > > > Where can I get rid of this variable ? I see no easy way. > > > Currently I use gvim as default text editor within KDE > > > environment ... > > > > > > In an xterm or such I could disable it, but how for KDE ?? > > > > As far as I understand it, this variable is set by the session management of the respective desktop (KDE in your case, GNOME in mine). Maybe you can workaround the problem by using a small shell script which unsets SESSION_MANAGER and than calls gvim? > > Yes I will try to write a wrapper script around gvim. > This way ... > > mv vim vim.bin > cat > vim <<- EOF > unset SESSION_MANAGER > vim.bin > EOF > chmod 555 vim > FWIW, the new behaviour of vim is caused by patch 6.2.015. I added 015 to BADPATCHES in the ports Makefile and reinstalled. gvim works as usual now. Karel.