[Octave-bug-tracker] [bug #52496] Command Window can't scroll up on Windows 10 v. 1709

[John W. Eaton]

Follow-up Comment #17, bug #52496 (project octave):

I have a System running Windows 10 and can duplicate the problem.

I'd be glad to fix this if I knew how.

Is there a way to set the "ForceV2" registry key to 0 just for Octave?  That
seems like the simplest fix for now.

My copy of Octave is installed in C:\Octave\Octave-4.4.0.  The octave.vbs
script is ultimately runs C:\Octave\Octave-4.4.0\bin\octave-gui.exe.

After seeing the comment on this page:

https://wpdev.uservoice.com/forums/266908-command-prompt-console-windows-subsystem-for-l/suggestions/7262751-parameter-to-launch-cmd-exe-in-legacy-mode

I tried to use regedit to set the ForceV2 key just for Octave by adding a key
under HKEY_CURRENT_USER\Console with the name
%SystemDrive%_Octave_Octave-4.4.0_bin_octave-gui.exe using a DWORD value of
0x00000000 (0).  This did not seem to have any affect.  I also tried without
the ".exe" suffix and using "C:" directly instead of %SystemDrive% but nothing
I tried seemed to work.

Maybe someone else who has a better understanding of the Windows Registry
better will have some ideas.


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/