octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #65550] Odd error running octave-gui.exe –gui


From: Vincent Fatica
Subject: [Octave-bug-tracker] [bug #65550] Odd error running octave-gui.exe –gui
Date: Tue, 2 Apr 2024 22:06:18 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?65550>

                 Summary: Odd error running octave-gui.exe –gui
                   Group: GNU Octave
               Submitter: vefatica
               Submitted: Wed 03 Apr 2024 02:06:17 AM UTC
                Category: Other
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 9.1.0
         Discussion Lock: Any
        Operating System: Microsoft Windows
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 03 Apr 2024 02:06:17 AM UTC By: Vincent Fatica <vefatica>
Octave 9.1.0 on Windows 10. Here’s the text of an error message box from
Octave.

Could not copy help collection to temporary
file. Search capabilities may be affected.
Cannot open collection file:
\scratch\build\mxe-octave-w64\usr\x86_64-w64-mingw32\share\octave\9.1.0\doc\octave_interpreter.qhc

That message only appears when I issue this command in the TCC (JPSoft)
shell.

    start D:\octave\mingw64\bin\octave-gui.exe --gui

The error does not occur if I issue the same command in another Windows shell
(CMD, Powershell, PWSH) or if I use it (without “start”) in Window’s
Start\Run dialog.

Two observations: “scratch” does not seem appropriate for Windows. Perhaps
the value of %TEMP% belongs there. And Octave does not try to access that file
in that location when it starts without error (so says SysInternals’s
ProcessMonitor).

And a question: What would trigger that error? If the TCC shell is (partially)
at fault, an answer to that question might help bring about a fix.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65550>

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]