X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:subject:from:to:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding; q=dns; s=default; b=aRZrsaQx89qEa1mYIeIVhFxQ3CY9bmo46jF6CsqHSCQ tuiyrv0S6N5b3pUQyonu1cHfY9WNMQauEMXHR1niEixDdk9T/MoeyuwZmsJqya5D q76+QrT5UvMJtzPauKh1RL1hzsaQFUbWgGYAeZ66aThN4SMJKyJMvrKOWIYK6gig = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:subject:from:to:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding; s=default; bh=hTCg9kkTj2qJsZWRXNNEFtiWztU=; b=qELEkwFeGB4HsQY5X myla6aDYlhZs7mP3HdlPTOjg8PRLjEDMdYdOsGR1W0RgWbWWUEK46zNYlVwZ4MyG lBzwpdixEPqKMenEijv7v9M2Nq6yPimvkAINHjZdEz6kNDk9qbj4t70Wo3BrgSX8 5DkbQD/7qKW4wKCSEyqz+fXHfI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Message-ID: <1433360045.14116.11.camel@cygwin.com> Subject: Re: Cygwin: vim causes bash to die From: Yaakov Selkowitz To: cygwin AT cygwin DOT com Date: Wed, 03 Jun 2015 14:34:05 -0500 In-Reply-To: References: <3EC211E2982D40B9BB6AA77E3BD6214E AT GatewayI5> <556BBA7B DOT 9020008 AT cygwin DOT com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On Mon, 2015-06-01 at 09:30 -0700, John Marsh wrote: > You have to run vim several times in the same terminal for the fault to > occur. I launch bash from a desktop shortcut, and it appears to be using > the conhost process. My bash terminal is configured with white background > and black text, and vim is configured with a light background. I've been > using cygwin since it first came out, and I've always launched bash and vim > this way, and never seen this problem before. In fact I have another > Windows 7 computer with an older version of cygwin that works fine. So it > seems that a bug has been introduced along the line. I'm wondering if it > has something to to with the ongoing terminal issues I've seen discussed in > the mailing list. > > I would like to submit a detailed problem report. How is this done? https://cygwin.com/problems.html -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple