bugGNU Octave - Bugs: bug #42867, Several bugs in the latest...


bug #42867: Several bugs in the latest development version of Windows GUI

Submitted by:  None
Submitted on:  Tue Jul 29 05:09:19 2014  
Category: GUISeverity: 3 - Normal
Priority: 5 - NormalItem Group: None
Status: FixedAssigned to: None
Originator Name: Nirmal SamuelOriginator Email: -unavailable-
Open/Closed: ClosedRelease: 3.8.1
Operating System: Microsoft Windows

Add a New Comment (Rich MarkupRich Markup):

You are not logged in

Please log in, so followups can be emailed to you.


(Jump to the original submission Jump to the original submission)

Tue Aug 5 23:28:39 2014, comment #14:

#1 was fixed with http://hg.savannah.gnu.org/hgweb/octave/rev/8449cc186059, however wont appear unil the gui-release branch is used.

John Donoghue <lostbard>
Project Member
Tue Aug 5 20:27:41 2014, comment #13:

Issue 5 : Thanks for finding that pathname fix to start vim.exe session as editor. I added quotes and it spawns a seperate window for vim.exe now. Sorry, i made a false alarm, without paying attention to that space in pathname.

Issue 4 : Consider this closed. It happened only once (and that was immediate session after installation). But now it works and color changes i make in "Editor styles" is reflected properly. When it comes to color, i would only ask for a fix to Issue #1.

Issue 1 : This is a minor bug in command window, but should be fixed sometime. I have set the background color to be black in both "terminal" tab as well as my "Editor styles" tab. My foreground color is set to green in both cases. Now, close the octave session, and restart the program. You can see that the startup information (before the prompt) is printed in green with black background. But, there is also a huge white patch in the background, that divides the whole command window into two. I am running version 3.8.1 with binaries dated June 15th, 14. Have not updated anything, since my installation on 7/11/14.

Seems from the first comment that Issue 1 is fixed in a build after i installed. If that is verified, then you can close this bug ticket. Thanks to all of you guys, for the GUI. It made my life so much easier during past 1 month. Good work.
- Nirmal Samuel.

Mon Aug 4 23:17:06 2014, comment #12:

Pushed patch to gui-release:

John Donoghue <lostbard>
Project Member
Mon Aug 4 19:09:08 2014, comment #11:

Corrected patch attached

(file #31836)

John Donoghue <lostbard>
Project Member
Mon Aug 4 19:02:51 2014, comment #10:

Nirmal, in comment #4 you are saying:
"I remember naming the file and saving it".
What do you mean by this?

Torsten <ttl>
Project Member
Mon Aug 4 18:59:55 2014, comment #9:

John, the patch works on linux as well except that there is missing a "not" in the message.

Torsten <ttl>
Project Member
Mon Aug 4 15:15:55 2014, comment #8:

How about this to prompt if there is an issue attempting to run the custom editor.

I've tested in Windows, but not Linux yet.

(file #31835)

John Donoghue <lostbard>
Project Member
Mon Aug 4 12:29:07 2014, comment #7:

I just tried with gvim on my machine and realized what is probally the issue.
You need quotes around the editors name if it has spaces in the path, so on my machine:
"c:\Program files (x86)\vim\vim73\gvim.exe" %f

John Donoghue <lostbard>
Project Member
Mon Aug 4 12:24:58 2014, comment #6:

Works under WInXP 64bit for me, using octave-3.8.1-5-installer.exe from mxeoctave.osuv.de.

So we are both doing the same thing:

1) Verify use custom editor is not selected.
2) Open c:\octavoctave-3.8.1\src\build_packages.m
3) Open the editor styles preferences, change the default background color (far right color box in each row) to a color (green??) and press OK.
Does the test background all change?

1) change the use custom editor to:
c:\windows\notepad %f
2) press ok, and double click on a .m file from the file browser window in octave.

John Donoghue <lostbard>
Project Member
Mon Aug 4 10:31:35 2014, comment #5:

I don't think it will make any di have you tried 3.8.2 release candidate?

4. works for me still - I will try WinXp today if no one else gets to it first.

5. Works for me. I set it as:
c:\windows\write %f
And then double click on a file from the browser pane, and it opens up correctly.
If you get the path incorrect, then it will not complain, which is not optimal.

What are the editor features missing from the gui?

John Donoghue <lostbard>
Project Member
Mon Aug 4 06:05:26 2014, comment #4:

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 Files\GNU\vim\vim74\...
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.

Sun Aug 3 09:01:27 2014, comment #3:

I have copied issue 2 (Ctrl-C) into the report for bug #37672 which is about Ctrl-C in the GUI.

Issue 4: Was the file that was currently open an unnamed one (not yet saved) or a text file (*.txt)? In the first case the octave styles should have effect, in the latter case the Bash styles.

Is issue 5 working when you are using the full path of the editor programs?

Torsten <ttl>
Project Member
Wed Jul 30 05:06:26 2014, comment #2:

3. This is a special case because you are editing the file where octave stores the most recent files that were opened in the editor. In the first message box, press "Yes" to reload the file where "qt-settings" was stored as most recent file. In the next message box press "No" because the most recent file was just overwritten with the same entry.

I have pushed a changeset (gui-release) that checks if the first entry in the mru list is already the actual file name. This prevent the second and all following message boxes.

Torsten <ttl>
Project Member
Wed Jul 30 00:50:31 2014, comment #1:

1. The background color was fixed in the gui-release branch (42128).

2. There has been a few bugs for this in the past - not sure if any still open. It behaves the same for me with your script.

3. Press No

4. works for me in 4.8.2 - you need press OK for them to take effect.

5. It works on 3.8.2 for me - you need to have the full path of the editor.
What 'features' of the editor do you need that are missing?

John Donoghue <lostbard>
Project Member
Tue Jul 29 05:09:19 2014, original submission:

I installed the version, that is clearly tagged as "non-release" version that is under development. But i needed the GUI in MS Windows platform, and so, i installed it to test it. Following are the bugs i noticed:

1. Changing color of command window, at program startup, did not change background color properly.

2. Run the following script. Then press control-C twice when it pauses. We get prompt. Press Control-C again to abort.
Now press control-c again, to see program crash.

3. File->Recent Editor Files->open qt-settings file (present under $HOME/.config directory. Pop up window says "It seems .... file has been modified by another program. Do you want to reload it ? " Click on YES, to see the infinite loop.

4. Editor style preferences are not working. (forground/background color- default)
Once applied, the windows that are currently open, should change color.
I noticed this, soon after installation, when i went to change settings, before
i started using the editor. There was only one file open (this text file) at this time.

5. Last, but most important for me: File Menu -> Preferences -> Editor tab -> Use Custom Editor, is not working. I tried both vim.exe and gvim.exe which are installed on my MS-Windows XP machine. Both are not working. Default editor seems to work, but does not have features that a developer needs.

Keep up the good work. I appreciate all the work you guys are doing, and providing this free software.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):

Attached Files
file #31836:  customeditor2.patch added by lostbard (1kB - application/octet-stream)
file #31835:  customeeditor-error.patch added by lostbard (1kB - application/octet-stream)


   bug dependencies.

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by ttl (Posted a comment)
  • -unavailable- added by lostbard (Posted a comment)
  • -unavailable- added by None (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat Aug 23 12:47:53 2014ttlStatusNeed Info=>Fixed
    Mon Aug 4 19:09:08 2014lostbardAttached File-=>Added customeditor2.patch, #31836
    Mon Aug 4 15:15:55 2014lostbardAttached File-=>Added customeeditor-error.patch, #31835
    Sun Aug 3 09:02:22 2014ttlStatusNone=>Need Info
    Wed Jul 30 00:50:31 2014lostbardDependencies-=>Depends on bugs #42128

    Back to the top

    Powered by Savane 3.1-cleanup