bugGNU Octave - Bugs: bug #64793, Command windows doesn't display...

 
 

bug #64793: Command windows doesn't display properly anymore

Submitter:  None
Submitted:  Thu 19 Oct 2023 10:04:47 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Duplicate Assigned to:  None
Originator Name:  Romain Toro Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 7.3.0
Operating System:  * Microsoft Windows Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 24 Oct 2023 02:01:15 PM UTC, comment #6: 

I don't think I saw that option. Would definitely have said yes if I did.
I checked in the Octave parameters though, and it says it is associated with .m files.

I found the solution thanks to that post:
http://savannah.gnu.org/bugs/?49707

Basically, I had to look in the registry, HKEY_CLASSES_ROOT which seems to contain all the file types associations. In the .m folder, the two keys I found were set to Octave.Document.7.3.0 where they should have been set to Octave.Document.8.3.0.
How it happened while I uninstalled and reinstalled properly the application eludes me.

Now it works correctly, thank you all for the help :)

Anonymous
Tue 24 Oct 2023 12:33:45 PM UTC, comment #5: 

When using the installer, there should be a page that asks if you'd like to associate .m files with Octave.

Does that work for you?

Closing the report because the original issue seems to be a duplicate of bug #62791.

Markus Mützel <mmuetzel>
Group administrator
Tue 24 Oct 2023 11:32:27 AM UTC, comment #4: 

Thank you very much Markus, it seems to work, the console doesn't shuts down any more.

Only problem left, the .m files are associated with Octave Launcher, but not with the GUI. I'd like the GUI to open without running the script when I click the .m file, like version 7.3 was doing.

I have been trying to find the solution online, but I read everywhere that I must set the default app to "Microsoft Windows based script host" or "wscript". I found wscript, but I got an error message "this app cannot be associated to files".

another solution would be to run an option --gui with the octave launcher associated with the files, but I didn't find how to do that :(

Anonymous
Tue 24 Oct 2023 07:01:57 AM UTC, comment #3: 

Microsoft changed the default console in updates for current versions of Windows. Octave isn't compatible to the new Terminal App yet.
See, e.g., bug #62791 or on Discourse:
https://octave.discourse.group/t/cli-is-open-together-with-gui-in-octave-7-1-on-windows-11/2753/6

Or the note in the README file that is displayed on installation of Octave:

> The Octave GUI is currently not compatible with the new Windows Terminal App. Please, switch the default to the (legacy) Windows Console Host for Octave to work correctly. See, e.g., these instructions[1] by Microsoft for how to change the default terminal and select "Windows Console Host".
>
> [1]: https://devblogs.microsoft.com/commandline/windows-terminal-as-your-default-command-line-experience/

Markus Mützel <mmuetzel>
Group administrator
Mon 23 Oct 2023 01:11:47 PM UTC, comment #2: 

Thank you for the quick answer Arun :)
It is funny that you would suggest trying version 8.3, because I actually did that, and I found a completely different problem with this solution xD

When I installed 8.3, at first it was working, but after a few runs I started having the following issue: when I launch the GUI, the background command line interface (which I assume to be also the engine), disappears, either after I run any script, or even right when the GUI opens. I am left with a GUI that does nothing when I click run button.

I tried reinstalling again, but the problem remains.

Anonymous
Thu 19 Oct 2023 03:45:54 PM UTC, comment #1: 

There were such problems in the past with the GUI on Windows but I thought they had all been fixed. Maybe they were fixed after 7.3.0. You may be able to work around it by deleting the GUI ini file as described here: https://octave.discourse.group/t/how-to-use-the-whole-command-window/3269/4

Also, is it feasible for you to try the latest stable version 8.3.0?

Arun Giridhar <arungiridhar>
Group Member
Thu 19 Oct 2023 10:04:47 AM UTC, original submission:  

Everything was working well, and then the GUI stopped working suddenly.
When I open Octave, through shortcut of by clicking my main.m file, the command window is completely garbled, like shown in the attached image. The code doesn't run either.

I tried reinstalling Octave 7.3 but it didn't work.

I have not made any change to the computer, except Dell hardware updates that are requested of me every week or so.

I work on windows 11 Enterprise, 22H2, my system is
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz   1.38 GHz
16Gb ram

thank you very much!

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #55258:  bug@Octave.png added by None (176KiB - image/png)

 

Carbon-Copy List
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by arungiridhar (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-10-24 mmuetzel StatusNone Duplicate
        Open/ClosedOpen Closed
        Dependencies- Depends on bugs #62791
    2023-10-24 mmuetzel Dependencies- bugs #64809 is dependent
    2023-10-19 None Attached File- Added bug@Octave.png, #55258

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code