[fossil-users] Command-line wildcards

2013-08-21 Thread fossilscm . zoc
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

Re: [fossil-users] Command-line wildcards

2013-08-21 Thread fossilscm . zoc
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, fossilscm@xoxy.net wrote: I actually wanted to simply post

Re: [fossil-users] Command-line wildcards

2013-08-21 Thread fossilscm . zoc
@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

Re: [fossil-users] Command-line wildcards

2013-08-21 Thread fossilscm . zoc
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 fossilscm@xoxy.netwrote: @Jan: Nope it's not fixed in 1.26. In fact

Re: [fossil-users] Command-line wildcards

2013-08-21 Thread fossilscm . zoc
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

2013-08-21 Thread fossilscm . zoc
@ 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

Re: [fossil-users] Command-line wildcards

2013-08-21 Thread fossilscm . zoc
@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-08-21 Thread fossilscm . zoc
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

Re: [fossil-users] Command-line wildcards

2013-08-21 Thread fossilscm . zoc
@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

2013-08-21 Thread fossilscm . zoc
@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