[Top][All Lists]

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

[Octave-bug-tracker] [bug #53070] Empty search path when running Octave

From: Peter Langer
Subject: [Octave-bug-tracker] [bug #53070] Empty search path when running Octave from a network share (UNC path)
Date: Wed, 7 Feb 2018 03:52:38 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko

Follow-up Comment #6, bug #53070 (project octave):

I have to apologize a little bit. The reason for the empty search path in
Octave is not the network share! It’s the way I start Octave. With my own
batch script I always started the octave.bat. But when I do that, I do not use
cmd.exe but the TCC/LE command prompt replacement from jpsoftware. (The reason
for the use of TCC is the not supported unc-path in cmd.exe.) 
Using TCC to start octave.bat leads to the problem with the empty search path
in Octave. (It has to be the start command in the octave.bat …) It doesn’t
matter, if I start it from a network share or a local disk. The search path in
octave will be empty both ways. If I directly start the octave-gui.exe from
the bin directory everything is fine. So in my batch scripts I replaced the
octave.bat with octave-gui.exe and now Octave starts with search paths!
In my opinion the report can be closed. Markus thank you for your support. I
really appreciate that you took the time to answer my question!

Now I have a next question and don’t know: it’s a bug or a feature? If I
run my batch file by manually starting it on a local computer it is running
just perfect(Windows 7 Pro and Windows 2012 Server R2). If my batch file is
started trough the jobsystem in the HPC-cluster on a randomly chosen remote
computer(Windows 2012 Server R2) I get the following warnings:

warning: gl2ps_renderer::draw_axes: empty feedback buffer and/or nothing else
to print
warning: called from
    __opengl_print__ at line 169 column 7
    print at line 519 column 14
    test.m at line 158 column 1

It seems to me, that this has something to do with bug #44292. Should I open a
new bug-report?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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