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:mime-version:date:message-id:subject:from:to :content-type; q=dns; s=default; b=BIzXeaBrKpNQVvg9R8+7g9c7cA+p1 ZSO+AGFar9iJPDNoufyqd0dZQ+XVhhu89muqYXU8BJcWjWgzSArSsFR8EjwZtDyO +O5fkBTXHGQQ6n0XO1PLcMyHdk8gxYttOScEgB+EstG1jMkTpRRPqdpKNELmprql 1eiDkctYmxezYA= 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:mime-version:date:message-id:subject:from:to :content-type; s=default; bh=5xxP0nl4dfPikBFjO72ZS8KRYgc=; b=rEf JB1h8YuwjwRtcJuML5tZDSdJTAh5qabaF+jAIkz+1MxLGnR2wl1U+dt6zpHcwu9j wQTC/zHilzP7j1VK+dUgxiH/sD+a9MlVXMvHa3IAV7rWAta9YMqduVBhkRzBwB6w wAA9S7nOhUtR3fkdRstPC1/4Llkc362iAoj3CXVc= 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=2.6 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f176.google.com MIME-Version: 1.0 X-Received: by 10.180.94.168 with SMTP id dd8mr42944240wib.76.1438675282957; Tue, 04 Aug 2015 01:01:22 -0700 (PDT) Date: Tue, 4 Aug 2015 10:01:22 +0200 Message-ID: Subject: 2.2.0: possible bug with Vim 7.4.764 and syntax highlight From: Xealot To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Hello! There seems to be a possible bug with cygwin 2.2.0 in xterm terminal mode (default) and using vim 7.4.764 with syntax highlighting enabled. To verify and reproduce: echo "syntax on" >> ~/.vimrc vim -E The prompt at the bottom should now show an escape sequence: Entering Ex mode. Type "visual" to go to Normal mode. :]11;rgb:0000/0000/0000\ This causes issues when using vim as normal in this configuration because the inserted escape sequence seems to replace the first character in a given document with a 'g' when opened. The problem goes away when changing terminal type to vt100 or vt220 or if you downgrade vim to revision 752 available on some mirrors through the setup. -- 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