Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Thu, 26 Jul 2001 16:02:09 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.3.2-1: SEGV signal after vim start in mutt
Message-ID:	<20010726160209.C20780@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<200107261956 DOT OAA15208 AT symphony DOT cig DOT mot DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<200107261956.OAA15208@symphony.cig.mot.com>; from marcin.koren@motorola.com on Thu, Jul 26, 2001 at 03:01:04PM -0500

On Thu, Jul 26, 2001 at 03:01:04PM -0500, Marcin Koren wrote:
>Hi,
>
>I have upgraded CigWin to 1.3.2 recently. Vim crashes in this version
>if it is run from mutt. If you run Vim from shell everything is OK.
>If you run it from mutt you get the following message:
>
>[25;1HVim: Caught deadly signal SEGV
>Vim: Finished.
>
>The program versions I use are:
>
>Mutt 1.2.5i
>VIM 5.8
>
>I have found workaround/proper configuration. Instead of default setting
>TERM to CygWin you shall issue:
>
>TERM=linux
>
>BTW: Has anyone compiled VIM 6.x alpha to run in CygWin?

Is this the dreaded termcap buffer overflow problem?  Probably not since
vim seems to use ncurses.

Btw, it's not CigWin or CygWin.  It's "Cygwin".

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -