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 nothing of the sort happens. Each program is itself responsible for dealing with the arguments. Regards, Arjen On 2011-09-26 12:34, Emil Totev wrote: 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 [df9da91ba8] 2011-07-13 23:03:41 UTC Are there really so few people using fossil on Windows or am I missing something? Emil ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Wildcards not working on windows
On Mon, Sep 26, 2011 at 12:51 PM, Dmitry Chestnykh dmi...@codingrobots.comwrote: 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 like it does on Unix systems. http://cygwin.com/install.html -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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\t2fossil 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 cmd.exe definitely doesn't expand it: echo * * So what am I seeing here? :-) -- Dmitry Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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 a tiny webserver on the fossil machine that calls fossil in CGI mode and sets the SCRIPT_NAME environment variable appropriately based on the forwarded http header info. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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 Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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 dmi...@codingrobots.com 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 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 Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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 wildcard expansion code for Windows when porting Unix code. 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. -- Dmitry Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Wildcards not working on windows
On Mon, Sep 26, 2011 at 8:36 AM, Dmitry Chestnykh dmi...@codingrobots.comwrote: 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 Fossil releases using MinGW instead of MSVC? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Wildcards not working on windows
On Mon, Sep 26, 2011 at 2:36 PM, Dmitry Chestnykh dmi...@codingrobots.comwrote: 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. The good part of that is that it shows that fossil builds under MSVC :). PS: before someone says, but can't we get wildcard expansion running in MSVC as well? here's a link to more info about it: http://linux.die.net/man/3/wordexp wordexp() part of POSIX, so there _might_ be a version of it available for MSVC. That said, transforming wildcards to expanded CLI arguments is not a straightforward as it sounds (been there, done^H^H^H^Htried that). Complications include multi-word tokens (i.e. spaces, which hard-core Unix users never do but Windows users do regularly) and un/escaping of the values (e.g. who, at the API level, is responsible for escaping/unescaping) when normalizing expanded words into internal argument lists. Anyway... -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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 fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Wildcards not working on windows
Hi to make sure that wildcards get expanded on all MinGW versions ( http://www.mingw.org and http://mingw-w64.sourceforge.net), I include the following piece of code in main.c /* ** Enable command line globbing on MinGW. */ #ifdef __MINGW32__ # ifdef __MINGW64__ int _dowildcard = -1; # else int _CRT_glob = -1; # endif #endif For the Microsoft C compiler the following page explains how to enable wildcard expansion: http://msdn.microsoft.com/de-de/library/8bch7bkk%28v=VS.100%29.aspx I dont know if this also works with older compilers. -- tsbg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Wildcards not working on windows
On Mon, Sep 26, 2011 at 11:12 AM, Dmitry Chestnykh dmi...@codingrobots.com 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-Windows targets, specifically, electronic control units. We are not supposed to build Windows applications, but we are allowed. That said, my primary platform is not Windows and I seem to be the only one here willing to even try to build for a PC, whether Windows or Linux, so I would certainly prefer to not build Fossil on Windows myself. Also, our PC support people would prefer we got official builds from Fossil's (or other tool's) website.. Thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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: http://msdn.microsoft.com/de-de/library/8bch7bkk%28v=VS.100%29.aspx I dont know if this also works with older compilers. Aha, so there's way to expand wildcards with VS compilers without writing more code! Other versions drop down (on en-us page) shows that it's available on VS 2003, 2005, 2008, and 2010. -- Dmitry Chestnykh ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[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 worth the hassle... [1] - http://www.startssl.com/?app=33 Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
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 listening on the wire. (Of course, it seems governments *do* spend a fair bit of effort listening on the wires, but they're not likely to be interested in your fossil password. Make sure it's not more valuable than it needs to be by not using the same password for more than one thing!) Actually I'm sometimes using machines that I do control in a way, but never really setup - usually by means of live cd. On the other hand I'm working in an environment where we have people actively doing network security research. I think their ethics can be trusted, but still feel a bit uncomfortable every time I see a certificate warning. Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[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). That might also be something interesting (mainly cosmetic) to optionally (via th1 var?) add in the default fossil footer (page generated in XYZ ms). -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[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 JSON post: if you do not comment/complain about the JSON structures being returned by this API then i will end up making such decisions by myself and you might not like them. So feel free to pipe up at any time. Any and all feedback is considered (and it will be more strongly considered if the corresponding code is not already written!). With that in mind... A summary of what currently works: - The core error reporting routines now format errors in JSON form when running in JSON mode (==CLI 'json' command or HTTP /json path). - Logging in and out, including the anonymous user, with or without cookies. (We still have the 1 login/user limitation, though!) - Wiki: list pages, create new page, fetch/save individual pages - Branches: fetch list of all/open/closed branches - Admin: list users, fetch a specific user - Timeline: checkins, wiki, ticket (before and after search ranges work, other options are pending) - Misc.: server version info, repo stats, get current user's access rights, whoami - Access restrictions match the corresponding HTML-mode behaviours (and if they don't, it's a bug). - There's an ugly test/demo app and [an even uglier] prototype/proof-of-concept wiki editor: see ajax/*.html or the live demo [2] (caveat: on that site access is severely castrated, so you cannot test all features). (Side note: relatively little core code was touched. Primarily the core error reporting routines, a couple additions to the 'g' object, and the parsing of POSTed JSON data.) All of the working features are documented in the working draft[1]. (Just keep in mind that implemented/working doesn't necessarily mean will still work that way tomorrow!) i update the doc as features are added/changed, so check there or the commit timeline for updates. Once the API is more or less complete i'll move the docs into the repo (where they philosophically belong, but Google Docs is just way too convenient for the time being). The TODO list is still as long as my hair, and i seem to be adding two TODOs for every feature added, so there's a ways to go, but the functionality which is there appears to work fine and more is being added all the time. All of the basic infrastructure is in place and has been more or less stable for all of 2 or 3 days now, making it fairly easy to add new JSON interfaces. Happy Hacking! [1] = draft spec: https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/edit [2] = live demo (but no admin access for you!) http://fossil.wanderinghorse.net/repos/fossil-sgb/json/index.html -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
