Bug #13809 2008-05-13 23:55
chikigai
Editor saves file with uppercase letters to lowercase
Using: Nightly Build (SVN 5020) Windows Unicode under Windows XP SP3
Steps to reproduce:
1) Open a file (which contains uppercase letters in its filename on disk) from the "Build Messages" tab of the Message Pane by double clicking a warrning/error.
2) Edit the file in the Editor and save.
The filename is changed to lowercase on disk.
- Category
- Application::Editor
- Group
- Status
- Closed
- Close date
- 2008-06-01 07:42
- Assigned to
- biplab
History
Sorry, but I can't reproduce. Any additional information? Does it
still persist?
Problem still persists.
Tried Nightly Builds 5010 and 5000 but the same problem occurs.
The simplist way to reproduce would be to:
1) Create a project with 1 source file called "SOURCE.c"
2) add a "#error" statement in "SOURCE.c"
3) Close "SOURCE.c" from the editor
4) Compile
5) Error is detected by compiler and "SOURCE.c" is automatically opened in the editor but with the filename changed to "source.c"
6) Edit the source file and save
By the way, I am using VC 2008 Express as the compiler (this most probably isn't related to the issue).
As far as I can recall, I don't remember this happening with Builds 5010 and 5000.....
This is a wild guess, but the only change to my environment possibly triggering this problem I can think of, is that I have recently installed Windows XP Service Pack 3. (Service Pack 3 RC1 installed previously)
Will try downgrading to Service Pack 2 when I find the time.
Tried uninstalling Windows XP Service Pack 3 and reverted to Service Pack 2.
Problem still persists.
Then again, it could be one of those Microsoft things where uninstalling doesn't actually result in a "clean" uninstall...
Unfortunately, there's not much else I can try for the time being...
Verified that this issue does not occur on a different XP Box with Service Pack 3 installed.
The difference between the Box where the issue occurs is that Service Pack 3 RC1 was installed previous to installing the official Service Pack.
I think it's a safe bet to say that the installation of Service Pack 3 RC1 has done something to XP which is causing the problem.
In any case, this is most probably a Windows issue - bug should be closed.
Closed based on submitters request. Thanks for your feedback.