[Octave-bug-tracker] [bug #53938] Windows octave doesnt wait for --eval statements to complete

[Rik]

Update of bug #53938 (project octave):

                 Summary: windows octave doesnt wait for to --eval statements
to complete => Windows octave doesnt wait for --eval statements to complete

    _______________________________________________________

Follow-up Comment #6:

Any thoughts on this bug?  It seems like it should be resolvable without TOO
much trouble.

If I understand John D. correctly, Windows prefers the .exe extension to the
.bat extension when the same base file name exists.

Two easy possibilities suggest themselves:

1) On Windows only (ispc() or some such test), change definition of
octave_binary so that ext=".bat" in the following code.


octave_binary = fullfile (octave_bindir, sprintf ("octave-%s%s", ver, ext)); 


2) Alternatively, rename true executable to something like "octave.exe.exe". 
In this case, calling just "octave" would launch "octave.bat" since the
basename of the executable is now "octave.exe".  This would require updating
the .bat file to launch the correct executable, but hopefully the installed
desktop shortcuts were already launching the .bat file so there would be no
changes there.


    _______________________________________________________

Reply to this item at:

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

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