[EMAIL PROTECTED] wrote:
http://bugs.darcs.net/issue129
Two comments (and another plea to do things the unix way):
1. For the last couple of years that I've been tracking darcs, I've seen new
users request this change many times. I haven't counted, but it appears that
new users are going to continue to ask for this.
New users continually ask for a project to be just like the last project
they use so that they don't have a learning curve. New users are
sometimes, but not always, ignorant of their true needs.
2. In many cases, those new users have encountered a problem where some tool
was automatically processing the _darcs directory as though it contained data
instead of metadata. For example, the most recent case was that Eclipse was
compiling the source files inside _darcs, IIRC. I myself have had this problem
on more than one occasion when using recursive unix commands such as a
"dos-to-unix-line-endings fixer".
This debate continues to happen and yet 90%+ of the time the tool in
question (Eclipse being the perfect example) would do the _same_ thing
regardless of _darcs/ or .darcs/.
Of course, I use Windows primarily and for me both are arbitrary
choices. (I think the "." thing was a stupid "magic" choice in early
Unix history and should have been taken care of in more useful metadata.)
_darcs has the interesting factor of being Pythonic, btw. (Python uses
the _ as its magic representation for "private".)
The true fix here is not renaming _darcs/, its in stopping the current/
(pristine/) cache from appearing to be "real" files. David keeps
talking about a mini-filesystem approach. Of course an even
quicker/simpler fix might be to start filename mungling, such as simply
append ".darcs" to the end of every filename in current/.
--
--Max Battcher--
http://www.worldmaker.net/
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
