BUG: Opening read-only files that dont have file extensions.

[chuyler1]

I am a developer and we use MS Visual Source Safe for code management. When you check something in to VSS it makes your local copy read-only so you don't accidently make changes to it without checking it out again.

Sometimes I want to just view a file that is not checked out. I run into problems with TextPad when I try to open shell script files that don't have a file extension. I can open them fine when they are checked out (and not read-only), but when they are read-only TextPad locks up. TextPad will also lock up if I have the file open and I proceed to check it in (thus changing its permissions from read-write to read-only).

I am running Windows XP but I have witnessed this bug on W2K also.

[talleyrand]

Code: Select all

c:\>echo > foo
c:\>attrib +r foo
c:\>\progra~1\textpa~1\textpad foo

The file is read only, TP treats it as such and it is still responsive.

Code: Select all

c:\>attrib -r foo

The file (still loaded in TP) is now writable and TP is not locking up for me.
w2k, TP 4.7.1 Is the file checked out on the local machine or is it on network machine?

[chuyler1]

The file is on my local machine. When I check something out of VSS, it downloads the latest copy and makes it writeable on my local machine. When I check it in, it uploads the modified file and makes the local file read-only. I'm not sure what else Microsoft does in the background.

The "attrib -r foo" does not make it read-only on my WinXP machine. You have to right-click the file and select "read-only". However, I'm at home now and I can't seem to replicate the problem on my home machine

Perhaps there is something else that VSS is doing?

I'll double check the file properties when I get to work tomorrow.

[Bob Hansen]

The "attrib -r foo" does not make it read-only

The -r is to remove Read Only
Use +r to make it Read Only