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 20:20:00 +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 #13, bug #39822 (project octave):

Oh I could try that too (only setting TERM if it wasn't set). Easy fix, just
copy from a stanza higher up in octave-gui.cc.

Maybe we can ask Anirudha to make the MXE Windows installer such that Octave
is started with a batch file. After all, amending a batch file is much easier
than hacking around in the code. As I wrote in an earlier comment, it also
gives a chance to supply Octave with a somewhat cleaned-up environment (TERM,
esp. PATH, perhaps others).

As to your last question:
Setting TERM to cygwin does fix the pager. Good catch!
xterm, octave, dumb, vt100, and "" (empty) cripple the pager.


    _______________________________________________________

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]