[fossil-users] Wanted: adventurous JSON fans to take a test spin

Hi, all! With almost 90kb of new functionality and 21 pages of "draft spec" docs[1], the JSON branch has reached a point where some of you might be able to get some use out of it in your daily lives. But first, a quick public service announcement: as i mentioned in my first "drum up support for J

[fossil-users] does fossil or sqlite3 have a high-res (ms or better) timing mechanism?

Hi, all! Do any of you know if fossil or sqlite3 has a mechanism which would let me time the JSON responses with relatively high accuracy (ms or better)? i seem to remember seeing some code for that somewhere but cannot seem to find it (and don't know with certainty which source tree it was in).

Re: [fossil-users] Why the certificate on fossil-scm.org is invalid?

On Sep 26, 2011, at 11:39 PM, Joshua Paine wrote: >> having to think if someone is sniffing my password, every time I'm >> out of home > > If you're using machines you don't control, I'd say it's much more likely > that there's something nefarious logging activity on the machine than > listeni

Re: [fossil-users] Why the certificate on fossil-scm.org is invalid?

On 9/26/2011 5:07 PM, Remigiusz Modrzejewski wrote: valid certificates are given for free Thanks for the link! having to think if someone is sniffing my password, every time I'm out of home If you're using machines you don't control, I'd say it's much more likely that there's something nef

[fossil-users] Why the certificate on fossil-scm.org is invalid?

Hi, I'm wondering: why does fossil-scm.org use invalid certificate? This is pretty bad in times when valid certificates are given for free [1]. Is there some technical problem with that? I guess that not having to think if someone is sniffing my password, every time I'm out of home, may be wort

Re: [fossil-users] Wildcards not working on windows

On Sep 26, 2011, at 5:47 PM, Thomas Schnurrenberger wrote: > For the Microsoft C compiler the following page explains > how to enable wildcard expansion: > > > > I dont know if this also works with older compilers. Aha, so th

Re: [fossil-users] Wildcards not working on windows

On Mon, Sep 26, 2011 at 11:12 AM, Dmitry Chestnykh wrote: >> Should I make a point of always building future Fossil releases using MinGW >> instead of MSVC? > > If there are no issues with MinGW binaries, then I think, yes. > > Any Windows users want to chime in? My team does development for non

Re: [fossil-users] Wildcards not working on windows

Hi to make sure that wildcards get expanded on all MinGW versions ( and ), I include the following piece of code in main.c /* ** Enable command line globbing on MinGW. */ #ifdef __MINGW32__ # ifdef __MINGW64__ int _dowildcard = -1; #

Re: [fossil-users] Wildcards not working on windows

On 9/26/2011 11:12 AM, Dmitry Chestnykh wrote: Should I make a point of always building future Fossil releases using MinGW instead of MSVC? If there are no issues with MinGW binaries, then I think, yes. Any Windows users want to chime in? I don't mind if the Download build is from MinGW, bu

Re: [fossil-users] Wildcards not working on windows

> Should I make a point of always building future Fossil releases using MinGW > instead of MSVC? If there are no issues with MinGW binaries, then I think, yes. Any Windows users want to chime in? -- Dmitry Chestnykh ___ fossil-users mailing list foss

Re: [fossil-users] Wildcards not working on windows

On Mon, Sep 26, 2011 at 2:36 PM, Dmitry Chestnykh wrote: > Visual Studio compiler doesn't do such thing, so wildcards are not expanded > for binaries built on VS. > Richard seem to have released 1.19 binary for Windows compiled with Visual > Studio, while 1.18 > has been compiled with MinGW. Th

Re: [fossil-users] Wildcards not working on windows

On Mon, Sep 26, 2011 at 8:36 AM, Dmitry Chestnykh wrote: > > Richard seem to have released 1.19 binary for Windows compiled with Visual > Studio, while 1.18 > has been compiled with MinGW. > > Correct. I didn't realized there was a difference. Should I make a point of always building future Fos

Re: [fossil-users] Wildcards not working on windows

> Yes, this one works as expected. Great! > So it is a build issue? MinGW tries hard to make programs behave like they do on Unix. It seems like binaries compiled with it do shell-like expansion on arguments, before passing them to main() function. Thus, there's no need to write your own wil

Re: [fossil-users] Wildcards not working on windows

Yes, this one works as expected. So it is a build issue? Thanks Emil On Mon, Sep 26, 2011 at 2:40 PM, Dmitry Chestnykh wrote: >> What should matter here is that it DOES work with the previous fossil >> version (1.18) and does NOT work with 1.19 - so obviously _something_ >> changed in fossil its

Re: [fossil-users] Wildcards not working on windows

> What should matter here is that it DOES work with the previous fossil > version (1.18) and does NOT work with 1.19 - so obviously _something_ > changed in fossil itself. Here's a binary of the same version built with MinGW: http://www.dchest.org/temp/fossil.exe Does it work for you? -- Dmitry

Re: [fossil-users] How to set up a server under nginx ?

> OK. Well, the other thing you can do is lobby the nginx people to start > supporting CGI. :-) I'm not a nginx user, and such would not work if the front web server and the fossil server are on different machines, as they are in my case. With the current fossil code base my workaround is to run

Re: [fossil-users] Wildcards not working on windows

Well, I am normally using TCC/LE as my shell, but just confirmed it is the same with CMD.EXE. What should matter here is that it DOES work with the previous fossil version (1.18) and does NOT work with 1.19 - so obviously _something_ changed in fossil itself. Thanks Emil On Mon, Sep 26, 2011 at

Re: [fossil-users] Wildcards not working on windows

On Sep 26, 2011, at 1:13 PM, Dmitry Chestnykh wrote: > > So what am I seeing here? :-) Aha, it seems like main() for binaries build with MinGW actually receive expanded arguments in argv. Are Windows binaries available from the download page build with Visual Studio? -- Dmitry Chestnykh ___

Re: [fossil-users] Wildcards not working on windows

Hm, I just tried it on my Windows XP virtual machine in cmd.exe, and it works for me: C:\Dev\t2>fossil add * C:\Utils\fossil.exe: cannot add _FOSSIL_ ADDED sub/text1.txt ADDED sub2/text2.txt ADDED test.txt ADDED test2.txt I haven't found code for glob expansion in Fossil in add command, and

Re: [fossil-users] Wildcards not working on windows

On Mon, Sep 26, 2011 at 12:51 PM, Dmitry Chestnykh wrote: > On Sep 26, 2011, at 12:34 PM, Emil Totev wrote: > Windows cmd doesn't expand * to the list of files. > If you want to add all files in the directory, try this: > > fossil add . > Or use cygwin's bash shell, which behaves more or less lik

Re: [fossil-users] Wildcards not working on windows

On Sep 26, 2011, at 12:34 PM, Emil Totev wrote: > fossil add * > D:\utils\programs\fossil.exe: file not found D:/TEMP/proj/* Windows cmd doesn't expand * to the list of files. If you want to add all files in the directory, try this: fossil add . -- Dmitry Chestnykh ___

Re: [fossil-users] Wildcards not working on windows

Hi Emil, what you are missing is that it is not fossil itself that expands the wildcard, but the shell in which you invoke it. On Linux (UNIX, ...) the shell, Bourne shell or otherwise, expands the wildcard into a list of file names and fossil simply picks up the expanded names. On Windows nothi

[fossil-users] Wildcards not working on windows

Hi This is fossil version 1.19 [6517b5c857] 2011-09-01 18:25:19 UTC on Windows 7 SP1 fossil add * D:\utils\programs\fossil.exe: file not found D:/TEMP/proj/* Files are of course there, but it seems the wrong path separator is used (/). The same works OK with This is fossil version 1.18 [df9da91ba