P4 edit files not in client view

To move files already opened for edit from one changelist to another, use p4 reopen. Opens the files for edit within the specified changelist.

If this option is not provided, the files are linked to the default changelist. Keep existing workspace files; mark the file as open for edit even if the file is not in the client view. Use p4 edit -k only in the context of reconciling work performed while disconnected from the shared versioning service.

Preview which files would be opened for edit, without actually changing any files or metadata. For more information, see the section Support for exclusive locking in the Fetching and Pushing chapter of Using Helix for Distributed Versioning. Stores the new file revision as the specified type, overriding the file type of the previous revision of the same file. Because p4 edit turns local OS write permissions on for the specified files, this command should be given before the file is actually edited.

The process is:. To edit an older revision of a file, use p4 sync to retrieve the previously stored file revision into the client workspace, and then p4 edit the file.

Because this file revision is not the head revision, you must use p4 resolve before the file can be stored in the depot with p4 submit. By default, Perforce does not prevent users from opening files that are already open; its default scheme is to allow multiple users to edit the file simultaneously, and then resolve file conflicts with p4 resolve. To determine whether or not another user already has a particular file opened, use p4 opened -a file.

P4 the command line version is case sensitive. Thus when I was copying the file name from command line to P4V to check if the filed existed, P4V was correctly showing the file. With very minute observation I realized that one character in file path had a capital case, while the correct path as in small case.

This is how I stumbled upon your question. My answer may help others. Add a comment. Active Oldest Votes. Do: p4 sync file1 p4 edit file1. Improve this answer. Samwise Samwise On doing p4 sync file Maybe the file's not in the depot yet? If that's the case do p4 add file1. Sign up or log in Sign up using Google. Sign up using Facebook.

How can I add these files to my depot? Or to the client view so that I may successfully add them? Usually after installing Perforce to a new computer, when you try to sync Depot files the system gives sync error message "File s not in client view". Here is the solution:. After struggling with it for hours, I finally sort it out.

It's very simple, just Add your folder name to the mapping. My situation is the folder name is not the same as the workspace name "deport".

This will happen when you are not using commit or update the workspace for a long time. Select and Right click on the Workspace which you want to load it again and select "load". Then logoff and login perforce again will work fine. For those who had the exactly same problem when setting up a blank project: You will need to create a folder named exactly as the Workspace name in order for the path to be recognized by Perforce.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Perforce P4W error: file s not in client view Ask Question. Asked 8 years, 6 months ago. Active 1 month ago.