. I'll need to use it for a while to see.
The quotes might just be a simpler solution. Just something else to learn :-))
Thanks!
-Clark
From: Michael Richter
To: fossil-users@lists.fossil-scm.org
Sent: Sun, December 20, 2009 6:30:02 PM
Subject: Re:
t;
> ------
> *From:* Michael Richter
> *To:* fossil-users@lists.fossil-scm.org
> *Sent:* Sun, December 20, 2009 6:02:57 AM
> *Subject:* Re: [fossil-users] Path Separators
>
> The easiest immediate solution for you is to type "OPTION" at the TCC
&
of files, leaving the commit for a later time.
It would be handy to copy/paste those names from the "fossil status" output.
-Clark
From: Michael Richter
To: fossil-users@lists.fossil-scm.org
Sent: Sun, December 20, 2009 6:02:57 AM
Subject: Re: [fo
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
> I'm using Fossil on MS Windows under the TCC/4NT shell, and am mostly
> reall
> -- Forwarded message --
> From: Clark Christensen
> 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
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
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
pa
7 matches
Mail list logo
