[Octave-bug-tracker] [bug #42867] Several bugs in the latest development version of Windows GUI

[anonymous]

Follow-up Comment #4, bug #42867 (project octave):

Issue 3 :  Yes, i figured that i can get out of the infinte loop, by pressing 
NO.  But, the issue still stands, because there may be  people who really want
to click on YES.

Issue 4:  As i have mentioned,  this issue only surfaces soon after a fresh
installation.  The color changes are working, once it is installed, exited,
and then octave restarted.  I remember naming the file and saving it. After
installation, you can test it on Windows XP (if you have a machine available).
Not a big issue, but i thought i will report it anyways.

Issue 5: I am a software developer. So i tried all the standard tricks like
giving the full pathname, and trying various styles of slashes (since I am on
MS-Windows XP), to get to the file.  I have two executables  installed  at  
C:Program FilesGNUvimvim74...
I checked on the checkbox that says "USE CUSTOM FILE EDITOR" and tried 
vim.exe as well as gvim.exe.  Both of these were the latest releases of GUI
vim for MS-Windows platform. Today, i noticed that once i change to "USE
custom file editor", if i do not exit Octave, and immediately try to "OPEN A
FILE", nothing happens, and no error message is given either. System simply
shows an empty Editor tab, with standard menu options at top.



    _______________________________________________________

Reply to this item at:

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

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