Re: [fossil-users] Command-line wildcards

@Richard: My guess is that the one of the prebuild binaries was compiled with MinGW > and the other with MSVC. Just to provide some information so you can verify your guess: I've been using fossil since years now, (on XP, Vista, and now Win7,) and I updated regularly (though I can't be sure I go

Re: [fossil-users] Command-line wildcards

On Wed, Aug 21, 2013 at 7:43 PM, wrote: > @Stephan Beal: Thanks man. And I'll admit I might have been a tick too > sensible about it. :-) > ...Anyway, I did not want to go in too deep about the whole matter. I > thought you guys would want feedback on issues because it is a chance to > improve th

Re: [fossil-users] Command-line wildcards

@Stephan Beal: Thanks man. And I'll admit I might have been a tick too sensible about it. :-) I'm very well aware that Windows is a bloated piece of ... code full of deficiencies. But if something used to work well up to a certain version (I'm using fossil since years, could have been 0.something

Re: [fossil-users] Command-line wildcards

On Wed, Aug 21, 2013 at 3:18 PM, wrote: > Uh? My question was about the mailman mailing list?!? How is that related > to Windows? > Because your top-post came immediately after such a question i took it out of context. In any other respect, I take your response as rather... snobbish. Not sure >

Re: [fossil-users] Command-line wildcards

On Wed, Aug 21, 2013 at 9:23 AM, wrote: > Uhm, perhaps a naive "outsider" question, but how came the issue wasn't > there before 1.25, if it's the differences in how the different shells > process CLI arguments? Did the shells not remain the same in between? > > My guess is that the one of the pr

Re: [fossil-users] Command-line wildcards

Uhm, perhaps a naive "outsider" question, but how came the issue wasn't there before 1.25, if it's the differences in how the different shells process CLI arguments? Did the shells not remain the same in between? On Wed, Aug 21, 2013 at 3:02 PM, Mark Janssen - mpc.jans...@gmail.com < fossilscm.zo

Re: [fossil-users] Command-line wildcards

@Stephen: But since I must accept the culture of the place I'm visiting, perhaps you > can help out a novice mailman list fellow: Is there any way to only receive > emails from threads I am participating in? > i haven't used Windows (outside of customer sites and an occasional game of > Empire at

Re: [fossil-users] Command-line wildcards

2013/8/21 Mark Janssen : > Sorry for spamming, but with the change it works within msys, but it fails > on the windows command line. Seems like a bit of a Catch 22 caused by the > different idea windows and unix have about how to pass arguments. See:

Re: [fossil-users] Command-line wildcards

Sorry for spamming, but with the change it works within msys, but it fails on the windows command line. Seems like a bit of a Catch 22 caused by the different idea windows and unix have about how to pass arguments. On Wed, Aug 21, 2013 at 2:52 PM, Mark Janssen wrote: > Yes, for example fossil

Re: [fossil-users] Command-line wildcards

Yes, for example fossil add * will still do the right thing. On Wed, Aug 21, 2013 at 2:51 PM, Stephan Beal wrote: > On Wed, Aug 21, 2013 at 2:48 PM, Mark Janssen wrote: > >> I did not test this with the 64bit version of MinGW. Using an unquoted * >> in this case still works as expected. >> > >

Re: [fossil-users] Command-line wildcards

On Wed, Aug 21, 2013 at 2:48 PM, Mark Janssen wrote: > I did not test this with the 64bit version of MinGW. Using an unquoted * > in this case still works as expected. > "as expected" means, i assume: resolves to a list of all files matching "*" in the current directory? (That's the expected Uni

Re: [fossil-users] Command-line wildcards

Following change fixes it for met with MinGW 32 bit on windows 7. $ fossil diff src/main.c argc in wmain 3 --- src/main.c +++ src/main.c @@ -522,11 +522,13 @@ */ #if defined(_WIN32) && !defined(BROKEN_MINGW_CMDLINE) int _dowildcard = -1; /* This turns on command-line globbing in MinGW-w64 */ i

Re: [fossil-users] Command-line wildcards

On Wed, Aug 21, 2013 at 8:31 AM, wrote: > @ > Stephan Beal: So fossil is refusing to eat it's own "dog food" - or rather one > of its more unique assets: The integrated wiki and ticket system? :-) > > We find that anonymously contributed tickets and wiki are generally of low quality, and not the

Re: [fossil-users] Command-line wildcards

It's a problem with the way MinGW parses and passes the command line. When main is called in fossil, the arguments are already expanded. As for the fix, I am not sure yet. On Wed, Aug 21, 2013 at 2:36 PM, Stephan Beal wrote: > > On Wed, Aug 21, 2013 at 2:31 PM, wrote: > >> @ >> Stephan Beal:

Re: [fossil-users] Command-line wildcards

On Wed, Aug 21, 2013 at 2:31 PM, wrote: > @ > Stephan Beal: So fossil is refusing to eat it's own "dog food" - or rather one > of its more unique assets: The integrated wiki and ticket system? :-) > This problem is Windows-specific. In every Unix shell "*.css", '*.css" will be equivalent (they

Re: [fossil-users] Command-line wildcards

@ Stephan Beal: So fossil is refusing to eat it's own "dog food" - or rather one of its more unique assets: The integrated wiki and ticket system? :-) But since I must accept the culture of the place I'm visiting, perhaps you can help out a novice mailman list fellow: Is there any way to only rece

Re: [fossil-users] Command-line wildcards

Thanks for the advice. However, I had already tried the single quote thing earlier, but I dismissed it, because AFAIK single quotes are not handled as string delimiters in the Windows shell, and: $ fossil set ignore-glob *.xxx > $ fossil set ignore-glob > ignore-glob (local) *.xxx But:

Re: [fossil-users] Command-line wildcards

Just re-confirmed: $ fossil set ignore-glob "*.css" > Usage: fossil set ?PROPERTY? ?VALUE? > $ fossil ver > This is fossil version 1.26 [c9cb6e7293] 2013-06-18 21:09:23 UTC On Wed, Aug 21, 2013 at 2:10 PM, Zoran Isailovski wrote: > @Jan: Nope it's not fixed in 1.26. > > In fact I noticed it wi

Re: [fossil-users] Command-line wildcards

@Jan: Nope it's not fixed in 1.26. In fact I noticed it with 1.26, then regressed to 1.25 to check if the bug was there, then to 1.24. (I intentionally used the plus sign when referring to 1.25+) On Wed, Aug 21, 2013 at 1:56 PM, Jan Nijtmans - jan.nijtm...@gmail.com < fossilscm.zoc.1c6a0fe4b8.ja

Re: [fossil-users] Command-line wildcards

2013/8/21 Jan Nijtmans : > 2013/8/21 : >> In a directory that contains several .* files and subfolders, several *.css >> files and a single .php file, the following work fine with version 1.24, but >> only output a usage info with 1.25+ ("fossil: Usage: fossil set ?PROPERTY? >> ?VALUE?"): > > This

Re: [fossil-users] Command-line wildcards

On Wed, Aug 21, 2013 at 1:49 PM, wrote: > I actually wanted to simply post a bug report to the ticket system, but > it's telling me it will be deleted unless I go through the hoops of the > mailing list registration process. (Uh?!? Why then technically enable > anonymous ticket submissions in the

Re: [fossil-users] Command-line wildcards

2013/8/21 : > In a directory that contains several .* files and subfolders, several *.css > files and a single .php file, the following work fine with version 1.24, but > only output a usage info with 1.25+ ("fossil: Usage: fossil set ?PROPERTY? > ?VALUE?"): This is already fixed in version 1.26.

Re: [fossil-users] Command-line wildcards

Yes, I did. (That was my 1st thought, too.) Sorry, forgot to mention it. On Wed, Aug 21, 2013 at 1:51 PM, Richard Hipp - d...@sqlite.org < fossilscm.zoc.5877ad8d94.drh#sqlite@ob.0sg.net> wrote: > On Wed, Aug 21, 2013 at 7:49 AM, wrote: > >> I actually wanted to simply post a bug report to t

Re: [fossil-users] Command-line wildcards

On Wed, Aug 21, 2013 at 7:49 AM, wrote: > I actually wanted to simply post a bug report to the ticket system, but > it's telling me it will be deleted unless I go through the hoops of the > mailing list registration process. (Uh?!? Why then technically enable > anonymous ticket submissions in the

[fossil-users] Command-line wildcards

I actually wanted to simply post a bug report to the ticket system, but it's telling me it will be deleted unless I go through the hoops of the mailing list registration process. (Uh?!? Why then technically enable anonymous ticket submissions in the 1st place?) Oh well... My findings: In a direct