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. _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
