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

[Philip Nienhuis]

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

Hmmm... I do not see that: no \e[K, Bksp works as-it-should.

<Maybe a bit OT:>
Intruiging, because MXE is meant to provide a standardized build environment.
Maybe some blame for our different experiences lies at my side:
- I still use MXE v. 0.0.3 to cross-compile on my Linux box ("parent:
3106:6d580645fd22")
- MXE 0.0.11 doesn't work for me (using OpenBLAS; it gets stuck with complains
about dllwrap, I haven't tried with traditional BLAS yet)
- My native MXE/MinGW build chain (also several months old) only allows Octave
to be built with make => installer can't be built there => Octave can only be
run with ./run-octave [1]

How do you build Octave?

OK, I just updated MXE-0.0.11 on my linux box and started anew; and if can
find time today I'll update my native MXE on my other (WinXP) box as well.
Maybe - but not hopefully ;-) - I get the same issues as you...

----------------
[1] which is no big deal as my whole motive for native MXE windows builds was
just to be able to debug/experiment with them with minimum hassle.

    _______________________________________________________

Reply to this item at:

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

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