X-Recipient: archive-cygwin@delorie.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
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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.JOHNER@cea.fr>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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

