[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49191] working directory spoiled after run of
[Octave-bug-tracker] [bug #49191] working directory spoiled after run of mkoctfile
Mon, 26 Sep 2016 18:23:44 +0000 (UTC)
Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Update of bug #49191 (project octave):
Status: None => Works For Me
Follow-up Comment #1:
Thanks for your bug report. Can you show a complete example demonstrating this
effect? I am unable to reproduce it. I have tried compiling an oct file in the
current directory as well as a different directory, either in or out of the
load path, and scripts in the current directory continue to work.
In addition to a complete session example, it would be helpful to show what
pwd and path show before and after this happens.
Reply to this item at:
Message sent via/by Savannah