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

[Philip Nienhuis]

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

Well the Del key does what it is supposed to do.

Esc doesn't work here; it just puts the cursor one char to the left, but not
always. I haven't been able to pinpoint the exact pattern.

INS key: doesn't work as it should, it just advances two chars to the right
and switches the underlying two chars to uppercase. After having used the INS
key on a line, Backspace and DEL don't erase anymore, Backspace only works
like left-arrow and DEL does nothing.
After <Enter> they works again on a new command line.

HOME and END do work. Nice! I use these keys a lot.

TAB when editing a command line only triggers the beeper. But Shift-TAB a few
times puts focus on the main menu bar, the same number of TABs get me back to
the command line and the next TAB beeps again.

As to the TERM environment setting: do we really need to set it in
octave-gui.cc? Can't they be inherited from the environment?
Octave on Windows can also be started from a batch file. The ones I use look
like:


@echo off
rem     Optionally clean up Windows PATH (antivirus, Powershell, etc
rem    Uncomment below for a clean PATH
rem set PATH= <cleaned up path>

rem    Add <OCTAVE_HOME>/bin to the PATH
set PATH=X:/Octave/Octave-3.7.6+_MXE/bin;%PATH%

rem    Spawn Octave
start octave.exe
exit


Before the start command other environment vars can be set as well. I've
experimented with TERM (with the settings in octave-gui.cc disabled) but
admittedly I couldn't discern much differences in behavior in the terminal.


    _______________________________________________________

Reply to this item at:

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

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