Re: [fossil-users] Path Separators
-- Forwarded message -- From: Clark Christensen cdcmi...@yahoo.com To: fossil-us...@lists.fossil-scm.org Date: Fri, 18 Dec 2009 09:36:43 -0800 (PST) Subject: [fossil-users] Path Separators 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 I was also trying to use fossil under TCC, but I had problems with the space in the default COMSPEC location (c:\Programs Files... etc). Finally I gave up and now I have an alias FOSS=CMD /C D:\PROGRAMS\UTILS\FOSSIL.EXE This seems to work OK (I'm a quite basic fossil user yet though). I would be happy if fossil were made to work better under TCC and am willing to help with testing and suggestions (no coding in C). Emil ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Path Separators
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
Re: [fossil-users] Path Separators
Clark Christensen wrote: 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 Easy workaround unless/until fossil is changed would be to use the http://www.cygwin.com/ bash shell. -- Daniel JB Clark | Sys Admin, Free Software Foundation pobox.com/~dclark | http://www.fsf.org/about/staff#danny ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
