octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #39822] Incorrect GUI terminal key mappings on Windows
Date: Sat, 31 Aug 2013 18:30:56 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6

Follow-up Comment #10, bug #39822 (project octave):

ESC
OK, I figured it would cancel the current command line. Not so then. Maybe
later.

My previous post was about testing on Win7 64 bit. On XP (32b) the INS key
merely inserts a tilde and beeps. It doesn't do anything else.
The other keys work like I described in comment #8.

TERM setting
On Octave 3.7.5 (MXE built) and all other builds before your patch, getenv
("TERM") gets me:

ans =


Setting TERM in a batch script before starting Octave returns the proper
environment setting in getenv(), yet behavior at the terminal prompt is
unchanged no matter what setting: cygwin, xterm, octave, whatever.

TAB
The TAB key already worked (in the sense of auto-completion of a few typed
characters) before your patch. My "complaints" (see original post) were
triggered by the untractable shifting of focus in case of an empty command
line.

Anyway, HOME and END do work now, which -for me at least- is a great
improvement, thanks.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39822>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]