This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: 1.3.2-1: SEGV signal after vim start in mutt
- To: cygwin at cygwin dot com
- Subject: Re: 1.3.2-1: SEGV signal after vim start in mutt
- From: "Marcin Koren" <marcin dot koren at motorola dot com>
- Date: Thu, 26 Jul 2001 15:51:25 -0500
On Thu, Jul 26, 2001 16:02:09PM -0400, Christopher Faylor wrote:
> 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
Sorry for typos. Cygwin is terrific :-)
Please add me on CC:, I am not subscribed to the distribution list.
Thnx,
Marcin
--
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/