The easiest immediate solution for you is to type "OPTION" at the TCC command line and tell TCC to allow both forward and back slashes in file names. CMD.EXE users have a bigger problem.
2009/12/19 Clark Christensen <cdcmi...@yahoo.com> > I'm using Fossil on MS Windows under the TCC/4NT shell, and am mostly > really happy with it. But the one thing that causes me the most problems is > the forward slash path separator in the output from many fossil commands. > > I often find myself using "fossil status", then wanting to copy/paste a > path/to/file from the output into the next command, perhaps "fossil gdiff". > Obviously, on Windows, this fails. And it's a hassle to have to edit the > path separators every time. > > How do other Win/Fossil users handle this? > > Would it make sense to change Fossil to output backslashes as the path > separator on Windows platforms (path\to\file)? > > Has this already been discussed? > > Thanks! > > -Clark > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
