X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.4 required=5.0 tests=AWL,BAYES_20,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Subject:	Re: About mouse selection in a cmd console
Date:	Thu, 5 Aug 2010 17:06:55 +0200
Message-ID:	<1299EF3181B10F479D85C328013285240331C4D4@THEZE.intra.cea.fr>
From:	"JOHNER Jean 066030" <Jean DOT JOHNER AT cea DOT fr>
To:	<cygwin AT cygwin DOT com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 4 August 2010 18:46, Andy Koppe wrote:
> This flag ensures that mouse events, including right clicks, are
> placed into the console input buffer rather than triggering window
> actions. That's in case an application activates xterm-style mouse
> reporting. Yep, the Cygwin console driver does indded support that,
> but vim doesn't know that, so you need to tell it via .vimrc:
>
> set mouse=3Da
>set ttymouse=3Dxterm2

Thank you, Andy, for sharing this incredible expertise.
Mouse control works with the above setting.

With "Quick Edit mode" enabled, mouse control is lost even in a standard
cmd console using Windows Vim.
That is a bug (or a feature) of Windows console Vim. I opened a thread
on vim_use to see if this can be improved.

Best regards,

Jean Johner

--
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

- Raw text -