On 2013-11-29 20:15, Matt Welland wrote:
Windows cmd.exe leaves wildcard expansion to the application, a choice
that seems really moronic to me but perhaps there was a good reason for
it.
It makes sense, but only in the context of another choice. Going back
to MS-DOS days, and into the early
On Fri, Nov 29, 2013 at 8:15 PM, Matt Welland wrote:
> Windows cmd.exe leaves wildcard expansion to the application,
The C runtime that fossil is built with does wildcard expansion,
although it doesn't work quite the same as most unix shells.
___
fossil
> So sometimes fossil does the expanding and sometimes it doesn't? Curious. I
> haven't done much on Windows in quite some time and I don't have a Windows
> machine handy to try it out on. Perhaps I was remembering use of cygwin.
>
> Either way if it is inconsistent then I suppose that may be somet
On Fri, Nov 29, 2013 at 6:36 PM, Ory Drilon wrote:
> > I'm going to hazard a guess that you are on windows? I speculate that
> one of
> > the shells listed here
> > http://en.wikipedia.org/wiki/List_of_alternative_shells_for_Windowsmight
> > expand the wildcard before handing the list to fossil.
> I'm going to hazard a guess that you are on windows? I speculate that one of
> the shells listed here
> http://en.wikipedia.org/wiki/List_of_alternative_shells_for_Windows might
> expand the wildcard before handing the list to fossil.
>
> Windows cmd.exe leaves wildcard expansion to the applicati
I'm going to hazard a guess that you are on windows? I speculate that one
of the shells listed here
http://en.wikipedia.org/wiki/List_of_alternative_shells_for_Windows might
expand the wildcard before handing the list to fossil.
Windows cmd.exe leaves wildcard expansion to the application, a choic
I find myself having to commit only subsets of changes, but having to
type in the full path for each file in the subset is a pain. I've
tried wildcarding, but fossil doesn't recognize the asterisks. Is
there some shorthand I can use to refer to the files in a subset?
___
7 matches
Mail list logo
