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

[Philip Nienhuis]

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

<OT>
True, configuring with --disable-jit makes the MXE-build succeed. 
In later MXE versions --enable-jit is the default.

BTW I was wrong to surmise that Octave was already built, the "dlname is empty
in dldfcn/__delaunayn__.la!" build error occurs half way.
I'll try to investigate further, but I have limited time for it this week.
</OT>

On-topic:
As to the key mappings, I think working HOME and END keys + cygwin TERM
setting made usability significantly better. 
A 3.7.6+ dist target patched for that can be built with Anirudha's mxe tree,
mxe-0.0.3 and mxe-0.0.11 (all cross-builds).
But I still do not see \e[K on startup of Octave with any of those mxe
builds...

Do you build a complete installer and run octave from there, or do you just do
./run-octave? Could that be the cause of that startup \e[K echo?


    _______________________________________________________

Reply to this item at:

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

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