X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Date: Thu, 5 Jul 2012 13:45:23 +0200 From: Lars =?iso-8859-1?Q?Bj=F8rndal?= To: cygwin AT cygwin DOT com Subject: Re: Alt+numpad keys doesn't work in ssh sessions Message-ID: <20120705114523.GL4600@lamasti.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 On Wed, Jul 04, 2012 at 09:48:16AM -0400, Earnie Boyd wrote: > 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. I tried that, but no difference. Thanks anyway. Lars -- 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