|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #55681] octave --no-init-file still uses finish.m and startup.m in the current directory |
Date: | Fri, 8 Feb 2019 19:07:15 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Update of bug #55681 (project octave): Status: None => Confirmed _______________________________________________________ Follow-up Comment #1: Yeah, I've known about this for a while. It was just a low priority. There are other weird cases as well. If you change the path so that __finish__ is not available then you get another error octave:1> cd .. octave:2> path ("."); warning: default load path altered. Some built-in functions may not be found. Try restoredefaultpath() to recover it. octave:3> exit error: feval: function '__finish__' not found error: ignoring const execution_exception& while preparing to exit This is also low priority. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55681> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |