X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 4 Jul 2012 09:48:16 -0400 Message-ID: Subject: Re: Alt+numpad keys doesn't work in ssh sessions From: Earnie Boyd To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q64DmnIu010257 On Wed, Jul 4, 2012 at 6:56 AM, Lars Bjørndal wrote: > Hello > > I use Cygwin from cmd.exe, because I use BRLTTY, and that doesn't work > in Minty. Inside Cygwin, I can type alt+066, and I get B as expected. If > I do the same after connecting to another host through ssh, nothing > happens. Is this a bug? I need the feature to type non native > characters such as quotation marks. On the remote host try setting the TERM variable to match what you have set locally. YMMV but I've seen this clear up some issues. -- Earnie -- https://sites.google.com/site/earnieboyd -- 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