On Fri, 2005-07-01 at 22:30 +0000, Jules Richardson wrote:
On Fri, 2005-07-01 at 13:15 +0200, Holly Bostick wrote:
- It *asked me* about things I might want to change-- and didn't make
assumptions about its own detection!! No, I really don't have a Windows drive, so you were right, but I don't want my c_drive in ~/.wine so put it somewhere else, thank you very much.
Out of interest (I'm sure it's documented *somewhere*) what is the reason for the C drive to be under ~/.wine such that it's 'hidden'?
It's always seemed strange given that copying data files to locations under the C drive seems a reasonable thing for users to do every so often, yet a lot of graphical file browsing tools won't show dot files / directories without reconfiguration.
Just seems an odd default to me, although not that big a deal. (I tend to do most of my work from a shell, so I don't care personally :-)
cheers
Jules
Not sure if it's explicitly spelled out somewhere, but it's sort of a standard to have an application store all of stuff in its own hidden folder. Now, Wine may be a bit of an exception to this, since it's not really one application or even suite of applications - the user has to install everything. However, keeping everything in .wine allows an easy, clean, nuke and reinstall of Wine, or transference of it to another system - one of the reasons this standard came about.
What we then are left with is a general usability question of where to put links to Wine's C drive folder. That's a distro or package level question, methinks.
Thanks, Scott Ritchie