RE: Saving Files in Octave

[Babson, John Freeman [AP]]

Dear Jordi and Louis,

Gentlemen, thank you very very much. Your hints proved most useful. Indeed, 
much as I suspected, I was overlooking the obvious. Unlike ET, my PATH did not 
phone HOME.

The default PATH on Mac OSX does not include either "/sw/bin" (we are using the 
fink installation) nor ".". Once I created a .bash_profile file in the with the 
appropriate additions everything works -- 'help', 'save', and 'load'.

Thanks again for your timely and helpful responses. Now we can go challenge 
some students.

John




________________________________________
From: address@hidden address@hidden on behalf of Jordi Gutiérrez Hermoso 
address@hidden
Sent: Tuesday, August 13, 2013 11:05 PM
To: Babson, John Freeman [AP]
Cc: address@hidden
Subject: Re: Saving Files in Octave

On 13 August 2013 03:20, Babson, John Freeman [AP]
<address@hidden> wrote:
> octave-3.6.4:8> save file1
> error: save: unable to open output file 'file1'

You likely are trying to write to a location that you don't have write
permissions to. What does "pwd" say? Is this pointing to a writeable
location? Do "cd /some/other/location" so that you may save the file.

HTH,
- Jordi G. H.

       
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
        Disclaimer:

This message (including any attachments) contains confidential information 
intended for a specific individual and purpose. If you are not the intended 
recipient, you should delete this message and notify the sender and The Hong 
Kong Polytechnic University (the University) immediately. Any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited and may be unlawful.

The University specifically denies any responsibility for the accuracy or 
quality of information obtained through University E-mail Facilities. Any views 
and opinions expressed are only those of the author(s) and do not necessarily 
represent those of the University and the University accepts no liability 
whatsoever for any losses or damages incurred or caused to any party as a 
result of the use of such information.