Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
However... It does work if you can't avoid it. I have no choice with our installshield source. There are two major issues I've dealt with: 1) Logistically, the command line has to escape the spaces somehow in referring to the modules. I use the command line cvsnt in a cygwin bash shell, and it works well with backslash escaping of the spaces on the command line. 2) The admin scripts (commitinfo, loginfo, etc.) just plain don't handle spaces in their specifications of modules, same with the modules file. I don't use them for these directories / modules, so I'm fine. (I think Tony's done some work here, but I'm not up on the details.) Boyd -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bo Berglund Sent: Friday, September 26, 2003 10:07 AM To: cvsnt at cvsnt.org Subject: Re: [cvsnt] Spaces On Fri, 26 Sep 2003 10:18:36 -0400, "Yang, Judy Bin" <jyang at atsautomation.com> wrote: > >Can the path folder of a CVS module or module name contain spaces ? Not recommended.... /Bo (Bo Berglund, developer in Sweden) _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook