Very insightful comments from Greg. Does anyone have any thoughts on filenames with whitespaces characters?
- Nick On Thu, May 30, 2002 at 08:30:32PM -0400, Nick Papadonis wrote: > > It appears ViewCVS has problems with filenames composed of > whitespaces. I think the problem is in 'loginfo-handler'. More >... > Is this a bug in ViewCVS or CVS itself? Did the CVS designers no > envision whitespaces in filenames? The latter: CVS is completely horked. It never dealt with the fact that filenames might have spaces. There is a patch in the SourceForge tracker (I believe) that tries to compensate. But even that is going to be a heuristic: if you can't find the file, then try to concatenate a couple arguments to see if the combination is a legal file. etc. [ maybe it can be more deterministic: if the files are passed with the ,v on the end, then you can assume any files *without* the ,v are the first word of a multi-word filename; I haven't looked into it ] I don't have any particular timeframes on when I'll get a chance to dig into this. I'd suggest trying out the patch from SourceForge and supply your feedback to the [EMAIL PROTECTED] mailing list. Cheers, -g _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
