|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #53938] Windows octave doesnt wait for --eval statements to complete |
Date: | Fri, 29 Jun 2018 17:06:14 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 |
Follow-up Comment #8, bug #53938 (project octave): To summarize and hopefully clarify, we now have .../Octave 4.4.0/octave.bat .../Octave 4.4.0/octave.vbs .../Octave 4.4.0/bin/octave.exe .../Octave 4.4.0/bin/octave-4.4.0.exe .../Octave 4.4.0/bin/octave-cli.exe .../Octave 4.4.0/bin/octave-cli-4.4.0.exe ... I think we should have this instead .../Octave 4.4.0/octave.vbs .../Octave 4.4.0/bin/octave.bat .../Octave 4.4.0/bin/octave-4.4.0.bat .../Octave 4.4.0/bin/octave-cli.exe .../Octave 4.4.0/bin/octave-cli-4.4.0.exe ... And optionally keep the copy of octave.bat at the top-level if that is considered useful. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53938> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |