How to make diff/merge windows writable?
Moderator: SourceGear
How to make diff/merge windows writable?
Hi,
I looked in the Knowledge base and I removed the commandline in Vault Client - Options: the text which looked like: /ro 2 and /ro 3. It still does not make those windows in my diff or merge window writable.
What is the correct way to make these files writable while I am doing a diff or merge?
Thanks
Pawan
I looked in the Knowledge base and I removed the commandline in Vault Client - Options: the text which looked like: /ro 2 and /ro 3. It still does not make those windows in my diff or merge window writable.
What is the correct way to make these files writable while I am doing a diff or merge?
Thanks
Pawan
I understand that completely. We are finding that even though our local files are checked out and writable, diff tool does not make it writable - the top right corner on the text window does correctly show that the file is writable.
In case of merge, the middle window which is supposed to be the merge output should be a temp file and should be writable - but it is not.
So my question is following: after I have removed those ./ro options, if the diff/merge tool is still not letting me edit those files, is that a known bug or we are doing something wrong?
-Pawan
In case of merge, the middle window which is supposed to be the merge output should be a temp file and should be writable - but it is not.
So my question is following: after I have removed those ./ro options, if the diff/merge tool is still not letting me edit those files, is that a known bug or we are doing something wrong?
-Pawan
That would definitely be a bug, but I'm not able reproduce what you are seeing.Pawan wrote:So my question is following: after I have removed those ./ro options, if the diff/merge tool is still not letting me edit those files, is that a known bug or we are doing something wrong?
When I take the /ro flags out, I can save changes to my working folder, but still can't save changes to other files (baseline files or temp copies of repository versions, because they actually are read-only on the file system).
Basically, with /ro flags out (and there are different arg strings for both diff and merge in the options screen), it is supposed to honor the file system setting for read-only. Have you checked in the actual working folder for whether the file is read-only, or is it possible that it is checked out, and edited, but still read-only for some reason?
So here is what I did:
1. I checked out a file from Visual Studio solution. I can happily modify this file in Visual Studio.
2. I went to Vault and selected file and chose "edit" option and edited it with notepad - it allowed me to change the file. Visual Studio prompted me to reload the file because notepad changed it.
3. In windows explorer, I checked if file was readonly - it is writable.
4. Now I selected "Show differences..." from Vault client. It showed me two panes - left one is repository and right one is my file on disk. It correctly highlighted the changes which I had through notepad.
5. It will not let me edit the right hand side pane which is the file on the disk.
Is this a bug? Are there file "owner" issues?
Thanks
Pawan
1. I checked out a file from Visual Studio solution. I can happily modify this file in Visual Studio.
2. I went to Vault and selected file and chose "edit" option and edited it with notepad - it allowed me to change the file. Visual Studio prompted me to reload the file because notepad changed it.
3. In windows explorer, I checked if file was readonly - it is writable.
4. Now I selected "Show differences..." from Vault client. It showed me two panes - left one is repository and right one is my file on disk. It correctly highlighted the changes which I had through notepad.
5. It will not let me edit the right hand side pane which is the file on the disk.
Is this a bug? Are there file "owner" issues?
Thanks
Pawan
I tried the steps above with VS 2003, and it seemed to work fine. Are you using another version of VS? (It probably wouldn't let Notepad save the file if it were locked by VS though, so that probably not the problem).
Try this: Under the same scenario, choose File->Open New File Diff from within sgdm, and open the same working folder file, and see whether it is writable. That way, we can tell whether the problem is the args passed in, or the file itself.
Try this: Under the same scenario, choose File->Open New File Diff from within sgdm, and open the same working folder file, and see whether it is writable. That way, we can tell whether the problem is the args passed in, or the file itself.
No - it does not.
What do you really mean by writable? By writable, I mean that I can go to that file pane and start typing anything I want in there. Is writable to you mean that you can click on those little diff "rectangles" in between the space between two panes which indicate the additions, deletions and changes? Or does it mean that I can type in that file pane like I can do in notepad or visual studio?
-Pawan
What do you really mean by writable? By writable, I mean that I can go to that file pane and start typing anything I want in there. Is writable to you mean that you can click on those little diff "rectangles" in between the space between two panes which indicate the additions, deletions and changes? Or does it mean that I can type in that file pane like I can do in notepad or visual studio?
-Pawan