Re: [fossil-users] [1.24/Win] Adding files through *.html?
On Thu, 29 Nov 2012 17:28:56 +0100, Gilles gilles.gana...@free.fr wrote: I guess it's due to the shell, but does a Windows user know of a work-around? Using the Fossil I compiled with MinGW, I noticed something strange: Running fossil add on a file that's already part of the repository, Fossil re-adds it: C:\Projects\Php\dummyfossil ls [...] Php/dummy/test2.html C:\Projects\Php\dummyfossil add *.html [...] ADDED Php/dummy/test2.html Is this standard? Thank you. ___ 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] [1.24/Win] Adding files through *.html?
On Mon, Dec 3, 2012 at 11:33 AM, Gilles gilles.gana...@free.fr wrote: On Thu, 29 Nov 2012 17:28:56 +0100, Gilles gilles.gana...@free.fr wrote: I guess it's due to the shell, but does a Windows user know of a work-around? Using the Fossil I compiled with MinGW, I noticed something strange: Running fossil add on a file that's already part of the repository, Fossil re-adds it: C:\Projects\Php\dummyfossil ls [...] Php/dummy/test2.html C:\Projects\Php\dummyfossil add *.html [...] ADDED Php/dummy/test2.html Is this standard? It is harmless. Thank you. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
On Thu, 29 Nov 2012 21:19:24 -0300, Richie Adler richiead...@gmail.com wrote: Thanks for the tip, but it's much more involved than simply fossil add *.html. Peter's solution is much more involved but compiling your own fossil executable is acceptable?! It's just that if possible, I'd rather use the same command at all times (fossil add myfile.txt, fossil add *.txt), rather than having to use a work-around. 1. BTW, if the MinGW version offers better support for shell use, why is the Windows binary compiled with MSVC? 2. Also, the Fossil wiki says: Note that Fossil requires the zlib compression library. This library is available by default on most unix systems, but it will typically have to be installed separately on windows systems. For windows builds, you may need to edit the makefile to tell it exactly where zlib is located on your system. Which files should I install where? Binaries + developer files? http://gnuwin32.sourceforge.net/packages/zlib.htm Thank you. ___ 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] [1.24/Win] Adding files through *.html?
2012/11/30 Gilles gilles.gana...@free.fr: 1. BTW, if the MinGW version offers better support for shell use, why is the Windows binary compiled with MSVC? The Windows binary is compiled with MinGW, only the commandline parser is replaced, in order to fix bugs like [13b7388964], [490b6c2edd] [cadc9aa78f], [d22946aa0c], all related to not using utf-8 on Windows. This parser doesn't do command-line expansion, just like MSVC and mingw-w64. Command-line expansion is an unique feature of MinGW, it is useful when using the Windows command line prompt, but is not expected in other situations. See also ticket [8ca2aae391], which contains Richard's remark how to finally fix that. 2. Also, the Fossil wiki says: Note that Fossil requires the zlib compression library. This library is available by default on most unix systems, but it will typically have to be installed separately on windows systems. That's fixed now, the wiki can be adapted: You don't need to install zlib any more on Windows in order to build fossil. ___ 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] [1.24/Win] Adding files through *.html?
On Fri, 30 Nov 2012 07:03:13 -0500, Richard Hipp d...@sqlite.org wrote: That has been fixed. The zlib sources are now included with the Fossil source code. So if you build from one of the latest Fossil version (not the ones on the Download page - they are too old - but rather a tree you get directly from the self-hosting repository) then if you don't have zlib sources on your system, the makefile will compile zlib itself using the sources in the fossil source tree and use that. Good to know, as the wiki still mentions Zlib and OpenSSL: www.fossil-scm.org/fossil/wiki?name=compillingOnWindows I'll start again with the latest source code. Thank you. ___ 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] [1.24/Win] Adding files through *.html?
On Fri, Nov 30, 2012 at 7:09 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2012/11/30 Gilles gilles.gana...@free.fr: 1. BTW, if the MinGW version offers better support for shell use, why is the Windows binary compiled with MSVC? The Windows binary is compiled with MinGW, only the commandline parser is replaced, That replacement command-line parser is not used on MinGW. Notice the !defined(__MINGW__) on this line: http://www.fossil-scm.org/fossil/artifact/a6c2200ac42a?ln=493 You can use the fossil test-echo command to check to test the command-line parser, to see what it does for your particular build. There is also a --hex option to fossil test-echo (in very recent versions) that shows you hexadecimal, to make sure it is handling UTF8 correctly. in order to fix bugs like [13b7388964], [490b6c2edd] [cadc9aa78f], [d22946aa0c], all related to not using utf-8 on Windows. This parser doesn't do command-line expansion, just like MSVC and mingw-w64. Command-line expansion is an unique feature of MinGW, it is useful when using the Windows command line prompt, but is not expected in other situations. See also ticket [8ca2aae391], which contains Richard's remark how to finally fix that. 2. Also, the Fossil wiki says: Note that Fossil requires the zlib compression library. This library is available by default on most unix systems, but it will typically have to be installed separately on windows systems. That's fixed now, the wiki can be adapted: You don't need to install zlib any more on Windows in order to build fossil. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
On Fri, Nov 30, 2012 at 7:12 AM, Gilles gilles.gana...@free.fr wrote: On Fri, 30 Nov 2012 07:03:13 -0500, Richard Hipp d...@sqlite.org wrote: That has been fixed. The zlib sources are now included with the Fossil source code. So if you build from one of the latest Fossil version (not the ones on the Download page - they are too old - but rather a tree you get directly from the self-hosting repository) then if you don't have zlib sources on your system, the makefile will compile zlib itself using the sources in the fossil source tree and use that. Good to know, as the wiki still mentions Zlib and OpenSSL: www.fossil-scm.org/fossil/wiki?name=compillingOnWindows I'll start again with the latest source code. You'll still need to find and install OpenSSL libraries if you want to use OpenSSL. You'll need this if you plan to support https: URLs. But that feature is off by default. Thank you. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
2012/11/30 Richard Hipp d...@sqlite.org: That replacement command-line parser is not used on MinGW. Notice the !defined(__MINGW__) on this line: http://www.fossil-scm.org/fossil/artifact/a6c2200ac42a?ln=493 In 1.24, this !define wasn't there yet. Since the introduction of this on trunk, the mentioned utf-8 bugs were re-introduced. Regards, Jan Nijtmans ___ 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] [1.24/Win] Adding files through *.html?
On Fri, Nov 30, 2012 at 7:20 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2012/11/30 Richard Hipp d...@sqlite.org: That replacement command-line parser is not used on MinGW. Notice the !defined(__MINGW__) on this line: http://www.fossil-scm.org/fossil/artifact/a6c2200ac42a?ln=493 In 1.24, this !define wasn't there yet. Since the introduction of this on trunk, the mentioned utf-8 bugs were re-introduced. The !defined(__MINGW__) was introduced in order to fix this bug: http://www.fossil-scm.org/fossil/tktview/8ca2aae39172f9 There have been no complaints since then. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
On Fri, 30 Nov 2012 13:09:44 +0100, Jan Nijtmans jan.nijtm...@gmail.com wrote: The Windows binary is compiled with MinGW, only the commandline parser is replaced, in order to fix bugs like [13b7388964], [490b6c2edd] [cadc9aa78f], [d22946aa0c], all related to not using utf-8 on Windows. This parser doesn't do command-line expansion, just like MSVC and mingw-w64. Command-line expansion is an unique feature of MinGW, it is useful when using the Windows command line prompt, but is not expected in other situations. See also ticket [8ca2aae391], which contains Richard's remark how to finally fix that. 2. Also, the Fossil wiki says: Note that Fossil requires the zlib compression library. This library is available by default on most unix systems, but it will typically have to be installed separately on windows systems. That's fixed now, the wiki can be adapted: You don't need to install zlib any more on Windows in order to build fossil. Thanks all for the infos. Compiling went flawlessly and it now supports fossil add *.c. ___ 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] [1.24/Win] Adding files through *.html?
2012/11/30 Richard Hipp d...@sqlite.org: In 1.24, this !define wasn't there yet. Since the introduction of this on trunk, the mentioned utf-8 bugs were re-introduced. The !defined(__MINGW__) was introduced in order to fix this bug: http://www.fossil-scm.org/fossil/tktview/8ca2aae39172f9 There have been no complaints since then. I don't think many people use chinese characters on the commandline on a non-chinese Windows version. It's when there is a code-page mismatch that the problem arises. I would like a solution that works in every situation. If MinGW would have support for an unicode commandline, as MSVC and MinGW-w64 have, that would solve everything. I don't know if MinGW-w64 supports Wsetargv.obj. If it does, that would solve everything as well. But even then, it would result in situations that the commandline-expansion is done multiple times, like when fossil_system() is called for running fossil.exe again, or when fossil is used in a Msys or cygwin shell. Then an -no-cmdline-glob option could disable the commandline globbing, just to be sure that nothing unexpected happens. However, unlikely in real life, since windows filenames cannot contain '*'/'?' Regards, Jan Nijtmans ___ 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] [1.24/Win] Adding files through *.html?
2012/11/30 Jan Nijtmans jan.nijtm...@gmail.com: Would switching the default build from MinGW to MinGW-w64 be an option? I tested the command-line expansion feature from MinGW-w64. It works! See [b1036fe5bf]. Should work on MSVC as well, but still untested. Doesn't work on MinGW, because they still didn't implement the -municode option. So, if a switch from MinGW to MinGW-w64 is an option, this could be a solution. Regards, Jan Nijtmans ___ 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] [1.24/Win] Adding files through *.html?
On Fri, Nov 30, 2012 at 8:32 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2012/11/30 Jan Nijtmans jan.nijtm...@gmail.com: Would switching the default build from MinGW to MinGW-w64 be an option? I tested the command-line expansion feature from MinGW-w64. It works! See [b1036fe5bf]. Should work on MSVC as well, but still untested. Doesn't work on MinGW, because they still didn't implement the -municode option. So, if a switch from MinGW to MinGW-w64 is an option, this could be a solution. The changes in the cmdline-expansion branch break the build for mingw32. Mingw32 does not recognize the -municode option. We have to continue to support Mingw32 - we cannot force everybody to upgrade to mingw64. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
2012/11/30 Richard Hipp d...@sqlite.org: The changes in the cmdline-expansion branch break the build for mingw32. Mingw32 does not recognize the -municode option. We have to continue to support Mingw32 - we cannot force everybody to upgrade to mingw64. Could some fallback option to built-in then? Such that the standard fossil.exe built by you is done with MinGW-w64. But that others can build fossil.exe with MinGW, doing the normal mbcs-utf-8 conversion. So, you (and Joe) make the switch, but don't force it for everyone. Would that be acceptable? So, if PREFIX = , then use main() and do mbcs-utf-8 conversion. for other PREFIX values, use wmain and do unicode-utf-8 conversion. Regards, Jan Nijtmans ___ 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] [1.24/Win] Adding files through *.html?
On Fri, Nov 30, 2012 at 11:02 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2012/11/30 Richard Hipp d...@sqlite.org: The changes in the cmdline-expansion branch break the build for mingw32. Mingw32 does not recognize the -municode option. We have to continue to support Mingw32 - we cannot force everybody to upgrade to mingw64. Could some fallback option to built-in then? Such that the standard fossil.exe built by you is done with MinGW-w64. But that others can build fossil.exe with MinGW, doing the normal mbcs-utf-8 conversion. So, you (and Joe) make the switch, but don't force it for everyone. Would that be acceptable? So, if PREFIX = , then use main() and do mbcs-utf-8 conversion. for other PREFIX values, use wmain and do unicode-utf-8 conversion. Can you suggest makefile changes to make this happen? Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
2012/11/30 Richard Hipp d...@sqlite.org: Can you suggest makefile changes to make this happen? Done in [2459ee7b71]. Biggest advantage: the parse_windows_command_line() is not necessary any more. Regards, Jan Nijtmans ___ 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] [1.24/Win] Adding files through *.html?
On Fri, Nov 30, 2012 at 11:45 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2012/11/30 Richard Hipp d...@sqlite.org: Can you suggest makefile changes to make this happen? Done in [2459ee7b71]. Biggest advantage: the parse_windows_command_line() is not necessary any more. I am unable to come up with a test case that the trunk does incorrectly that would work correctly in the cmdline-expansion branch. Can you suggest a reasonable test case? Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
2012/11/30 Richard Hipp d...@sqlite.org: I am unable to come up with a test case that the trunk does incorrectly that would work correctly in the cmdline-expansion branch. Can you suggest a reasonable test case? For MinGW, the cmdline-expansion does the same as trunk. However, it has the limitation that only characters from the current code-page can be used. But when compiled with MinGW-w64, that limitation doesn't exist any more: Any character can be used on the commandline can be used, no matter what the code-page is. I'll work out an example. Regards, Jan Nijtmans ___ 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] [1.24/Win] Adding files through *.html?
On Fri, Nov 30, 2012 at 12:06 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2012/11/30 Richard Hipp d...@sqlite.org: I am unable to come up with a test case that the trunk does incorrectly that would work correctly in the cmdline-expansion branch. Can you suggest a reasonable test case? For MinGW, the cmdline-expansion does the same as trunk. However, it has the limitation that only characters from the current code-page can be used. But when compiled with MinGW-w64, that limitation doesn't exist any more: Any character can be used on the commandline can be used, no matter what the code-page is. I'll work out an example. But other does commands like dir are also limited to showing only characters on the current code-page. At least in my experiments. I'm thinking that if dir cannot see the file, then it is OK for Fossil to not see it either. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
2012/11/30 Richard Hipp d...@sqlite.org: 2012/11/30 Richard Hipp d...@sqlite.org: I am unable to come up with a test case that the trunk does incorrectly that would work correctly in the cmdline-expansion branch. Can you suggest a reasonable test case? I'll work out an example. Here it is. Do the following (just cut-paste the following command to the Windows console, somewhere within a checkout): C:\Users\foo\workspace\fossiltype x Ω.txt Then type fossil add aaa and press (tab) followed by (enter). The windows console will show: C:\Users\foo\workspace\fossilfossil add Ω.txt fossil: not found: C:/Users/foo/workspace/fossil/O.txt But 'dir' will show the filename correct. What happens is that the Windows console can handle the greek Omega sign just fine, it's even in the console font! But when calling fossil, it's not in the current codepage, so Windows translates it to the most close thing: the character 'O'. Of course, the file is not found. When doing the same with the cmdline-expansion branch compiled with MingW-w64 or MSVC (any version), this example works as expected (I tested this with the latest MingW-w64 and with MSVC 10 express). MinGW is lacking the -municode option, that's why this cannot be fixed using MinGW. Regards, Jan Nijtmans ___ 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] [1.24/Win] Adding files through *.html?
On Thu, Nov 29, 2012 at 11:28 AM, Gilles gilles.gana...@free.fr wrote: Hello I'm getting another issue on an XP host trying to add multiple files to the next commit: D:\Temp\test.fossilfossil add *.html fossil: not found: D:/Temp/test.fossil/*.html D:\Temp\test.fossilfossil add *.html fossil: not found: D:/Temp/test.fossil/*.html D:\Temp\test.fossilfossil add ./*.html fossil: not found: D:/Temp/test.fossil/*.html What do these commands say? dir *.html fossil test-echo *.html FYI,fossil changes works fine to show me that some files have been edited, so Fossil is working OK. I guess it's due to the shell, but does a Windows user know of a work-around? Thank you. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
On Thu, 29 Nov 2012 11:32:06 -0500, Richard Hipp d...@sqlite.org wrote: What do these commands say? dir *.html fossil test-echo *.html D:\Temp\test.fossildir *.html Directory of D:\Temp\test.fossil 29/11/2012 17:19 5 dummy.html 1 File(s) 5 bytes 0 Dir(s) 303 243 038 720 bytes free D:\Temp\test.fossilfossil test-echo *.html argv[0] = [fossil] argv[1] = [test-echo] argv[2] = [*.html] It works with a single file: D:\Temp\test.fossilfossil add dummy.html ADDED dummy.html I've always tried using the full paths, to no avail: D:\Temp\test.fossilfossil add D:/Temp/test.fossil/*.html fossil: not found: D:/Temp/test.fossil/*.html ___ 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] [1.24/Win] Adding files through *.html?
On Thu, Nov 29, 2012 at 11:35 AM, Gilles gilles.gana...@free.fr wrote: On Thu, 29 Nov 2012 11:32:06 -0500, Richard Hipp d...@sqlite.org wrote: What do these commands say? dir *.html fossil test-echo *.html D:\Temp\test.fossildir *.html Directory of D:\Temp\test.fossil 29/11/2012 17:19 5 dummy.html 1 File(s) 5 bytes 0 Dir(s) 303 243 038 720 bytes free D:\Temp\test.fossilfossil test-echo *.html argv[0] = [fossil] argv[1] = [test-echo] argv[2] = [*.html] I think it will work better if you recompile using mingw instead of msvc. The crt0 for msvc does not process wildcards in command-line arguments whereas the crt0 for mingw does. It works with a single file: D:\Temp\test.fossilfossil add dummy.html ADDED dummy.html I've always tried using the full paths, to no avail: D:\Temp\test.fossilfossil add D:/Temp/test.fossil/*.html fossil: not found: D:/Temp/test.fossil/*.html ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
On Thu, Nov 29, 2012 at 5:35 PM, Gilles gilles.gana...@free.fr wrote: D:\Temp\test.fossildir *.html Directory of D:\Temp\test.fossil 29/11/2012 17:19 5 dummy.html 1 File(s) 5 bytes 0 Dir(s) 303 243 038 720 bytes free D:\Temp\test.fossilfossil test-echo *.html argv[0] = [fossil] argv[1] = [test-echo] argv[2] = [*.html] It works with a single file: D:\Temp\test.fossilfossil add dummy.html ADDED dummy.html I've always tried using the full paths, to no avail: D:\Temp\test.fossilfossil add D:/Temp/test.fossil/*.html fossil: not found: D:/Temp/test.fossil/*.html You can also do: for %x in (*.html) do fossil add %x /Peter ___ 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] [1.24/Win] Adding files through *.html?
On Thu, 29 Nov 2012 11:38:43 -0500, Richard Hipp d...@sqlite.org wrote: D:\Temp\test.fossilfossil test-echo *.html argv[0] = [fossil] argv[1] = [test-echo] argv[2] = [*.html] I think it will work better if you recompile using mingw instead of msvc. The crt0 for msvc does not process wildcards in command-line arguments whereas the crt0 for mingw does. I checked the strings within fossil.exe, but didn't find infos on who takes care of compiling Fossil for Windows to check how to recompile the code with Mingw. If the person in charge reads me, could you tell me? Thank you. ___ 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] [1.24/Win] Adding files through *.html?
On Thu, Nov 29, 2012 at 11:46 AM, Gilles gilles.gana...@free.fr wrote: On Thu, 29 Nov 2012 11:38:43 -0500, Richard Hipp d...@sqlite.org wrote: D:\Temp\test.fossilfossil test-echo *.html argv[0] = [fossil] argv[1] = [test-echo] argv[2] = [*.html] I think it will work better if you recompile using mingw instead of msvc. The crt0 for msvc does not process wildcards in command-line arguments whereas the crt0 for mingw does. I checked the strings within fossil.exe, but didn't find infos on who takes care of compiling Fossil for Windows to check how to recompile the code with Mingw. If the person in charge reads me, could you tell me? http://www.fossil-scm.org/fossil/doc/trunk/www/build.wiki Summary: (1) Install mingw/msys (2) Unpack the Fossil source tarball, or clone the fossil repository. (3) Run: make -f win/makefile.mingw (4) Put the resulting fossil.exe file somewhere on your path. Thank you. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] [1.24/Win] Adding files through *.html?
On Thu, 29 Nov 2012 17:43:34 +0100, Peter Spjuth peter.spj...@gmail.com wrote: You can also do: for %x in (*.html) do fossil add %x Thanks for the tip, but it's much more involved than simply fossil add *.html. ___ 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] [1.24/Win] Adding files through *.html?
On Thu, 29 Nov 2012 11:57:23 -0500, Richard Hipp d...@sqlite.org wrote: http://www.fossil-scm.org/fossil/doc/trunk/www/build.wiki Summary: (1) Install mingw/msys (2) Unpack the Fossil source tarball, or clone the fossil repository. (3) Run: make -f win/makefile.mingw (4) Put the resulting fossil.exe file somewhere on your path. Thank you. I'll give a try in the couple of days. ___ 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] [1.24/Win] Adding files through *.html?
Gilles decía, en el mensaje Re: [fossil-users] [1.24/Win] Adding files through *.html? del Jueves, 29 de Noviembre de 2012 14:08:32: On Thu, 29 Nov 2012 17:43:34 +0100, Peter Spjuth peter.spj...@gmail.com wrote: You can also do: for %x in (*.html) do fossil add %x Thanks for the tip, but it's much more involved than simply fossil add *.html. Peter's solution is much more involved but compiling your own fossil executable is acceptable?! Weird :) -- o-= Marcelo =-o ___ 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] [1.24/Win] Adding files through *.html?
On Thu, Nov 29, 2012 at 7:19 PM, Richie Adler richiead...@gmail.com wrote: Gilles decía, en el mensaje Re: [fossil-users] [1.24/Win] Adding files through *.html? del Jueves, 29 de Noviembre de 2012 14:08:32: On Thu, 29 Nov 2012 17:43:34 +0100, Peter Spjuth peter.spj...@gmail.com wrote: You can also do: for %x in (*.html) do fossil add %x Thanks for the tip, but it's much more involved than simply fossil add *.html. Peter's solution is much more involved but compiling your own fossil executable is acceptable?! Weird :) I think the issue is that *.html was simply an example. The actual use case involved more complex patterns than just *.html. Further note that compiling Fossil is really, really simply. For the latest code from trunk, there are no external library dependencies (other than the standard C library which comes with your compiler.) Installing Msys+Mingw is the hardest step, and that is still relatively simple. If you have never compiled Fossil from sources before, you really ought to give it a go. -- o-= Marcelo =-o ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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
