X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <83c75fec0802160005x476d4a3bq5c24b1774b6089d8@mail.gmail.com>
Date: Sat, 16 Feb 2008 11:05:04 +0300
From: "burning shadow" <burning DOT shadow AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New package: irssi-0.8.12-1
In-Reply-To: <47B69807.AE87380D@dessent.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
References: <announce DOT 42afa7b00802150709m171baffn8e9ecdc5e8fd05c0 AT mail DOT gmail DOT com> 	 <83c75fec0802151137gbb1aea6w9685590507a10a22 AT mail DOT gmail DOT com> 	 <42afa7b00802151311q695b173fr68821b2b30c973ff AT mail DOT gmail DOT com> 	 <83c75fec0802151708m53a3f8b1rd66f2d9d8a25d5dd AT mail DOT gmail DOT com> 	 <47B693C4 DOT 8060707 AT sh DOT cvut DOT cz> 	 <83c75fec0802152351j6e5d115jff10087d1d605cf7 AT mail DOT gmail DOT com> 	 <47B69807 DOT AE87380D AT dessent DOT net>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id m1G85aGp008828

Ok, this gonna be an offtopic, but how to make numpad keys work in vimwhen TERM set to xterm? It works perfect when TERM is cygwin.
On 2/16/08, Brian Dessent <brian AT dessent DOT net> wrote:> burning shadow wrote:>>  > Nope. Everything works fine only when TERM set to cygwin. For example,>  > numpad keys in vim. This is default setting for TERM and works>  > perfectly everywhere except that irssi build. And since my own compile>  > works just fine, I guess something wrong with the release than with my>  > terminal settings.>>  Václav is most certainly correct.  If you are not using a real Windows>  Command Prompt then TERM=cygwin is just plain wrong.  If it works, it's>  luck.  You should never have TERM=cygwin if you're using putty or any>  other terminal but a Windows Command Prompt.>>  Brian>>>  -->  Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple>  Problem reports:       http://cygwin.com/problems.html>  Documentation:         http://cygwin.com/docs.html>  FAQ:                   http://cygwin.com/faq/>>