Lars Nilsson writes:
When opening files on Windows, XEmacs does not maintain the filename
case for existing files.
While your request is plausible, I don't see that XEmacs necessarily
should preserve case if neither Windows nor cl.exe tries to, and if a
separate directory listing is required to get the file name, doing the
check is potentially expensive (the file may be on a network server).
I would like to stress that I would feel more comfortable if XEmacs
maintained the case for existing files (without me poking at stuff
I don't necessarily understand) regardless of what case was
specified in the request.
"Regardless" obviously is a non-starter; what if the user really wants
to change the case of the file name? So it becomes a question of
figuring out when XEmacs should implicitly change the command it
receives. This is not something that can be changed easily, we need a
lot more input from users with different use cases. I'm not in a
position to play with it myself, as I have no Windows hosts. Between
that and the issue of how to deal with network file systems, I don't
think this issue can be addressed quickly.
I can see two possibilities for existing tools or settings that would
work in your context. The first is that PCL-CVS may "do the right
Second, you could try setting `backup-by-copying' to t, which might
leave the directory entry of the file alone. You might also need to
disable auto-save or set `auto-save-visited-file-name' t.
XEmacs-Beta mailing list