Date: Tue, 15 Jul 2003 11:07:40 +0200 From: "Karel J. Bosschaart" <K.J.Bosschaart@tue.nl> To: Andreas Klemm <andreas@freebsd.org> Cc: current@freebsd.org Subject: Re: Vim: Caught deadly signal BUS (after -current update with new gcc) Message-ID: <20030715090740.GA77879@phys9911.phys.tue.nl> In-Reply-To: <20030714204643.GA14890@titan.klemm.apsfilter.org> References: <200307142038.h6EKciQ06885@mailgate5.cinetic.de> <20030714204643.GA14890@titan.klemm.apsfilter.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715090740.GA77879>