Re. File Saving Problem (Permissions issues).
Re. File Saving Problem (Permissions issues).
- Subject: Re. File Saving Problem (Permissions issues).
- From: "Matt Fox-Wilson" <email@hidden>
- Date: Tue, 31 May 2005 16:17:59 +1200
> From: Chris Espinosa <email@hidden>
>
> On May 24, 2005, at 7:56 PM, Matt Fox-Wilson wrote:
>
>> Ever since I started using XCode, I've been experiencing a problem saving
files. Basically, for various reasons my code is
>> stored on a Windows machine, and I connect to it by mounting a folder
using Samba. The files I wish to build (.cpp and .h)
>> are dragged in to my Xcode project, which locates them and builds them
with no problems.
>>
>> However, when I edit the files, particularly header files, I find I can
only save them once. If I try to save them a second
>> time, I get an error indicating that the file could not be saved. When I
look in the folder that contains the file, there's
>> a new file with the same name and a ~ appended before the suffix, and
that file cannot be deleted until XCode is closed.
>>
>
> The foo~.c is the backup file automatically saved by NSDocument for us.
Usually those files only last for a few milliseconds,
> then AppKit deletes them. Apparently in your configuration the backups
are not getting deleted when the underlying file is
> saved successfully, so future saves fail because the file can't be moved
to be the new backup (because the old backup is in
> the way).
>
> It would help to know the permissions of the directory on the smb server,
and whether the files are put there by a SCM system
> (e.g. Perforce).
Thanks for the thoughts there.
I'm not sure about checking the permissions locally on X (I've been way too
hands off that side of things :) but the Windows machine gives full access
to the user I'm logging in as. However, I'll try opening it to all users and
see if that helps. The files are being written by Visual Source Safe, which
is pretty simple and really only tweaks the read only flag. The permissions
all look good.
This may be coincidence but I have taken to having the folder containing the
original file open on my desktop while I work, and I can see it saving the
temp version briefly then removing it, and while I have been doing this I've
not had a single CPP complain at me, they've all saved fine. I've not tried
it with headers yet.
In reference to the other comment made (Hugh Sontag, Wed, 25 May 2005)
regarding a bug in the SMB driver since 10.3.7, I've had this problem since
10.2 (I think it was, it was with the first release of Xcode and its
equivalent OS) with header files.
Thanks for the suggestions, I'll try some permissions tweaking.
- Matt Fox-Wilson.
- email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden