Re: [fossil-users] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Robert
> If I want to use the creole parser in my projects what do I need to do then? It is difficult. 1) Check out and compile the creole branch yourself if you can, or ask someone else to compile it for you. 2) Persuade your users to use your binary rather than the official binary. 3) Make sure that

Re: [fossil-users] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Rene de Zwart
>> Robert thanks for the clarification. Is there a planning when the creole >> parser will be part of the trunk? > > No. The creole parser is my own little folly, not part of the main fossil > development, it is unlikely to be merged with the trunk. > > Best Wishes > -- > Robert If I want to use th

Re: [fossil-users] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Robert
Rene > My mistake. It wasn't clear to me that it worked like that. > All the better its already in there. I'm glad I was able to clarify the matter for you. > If you want to go to print a thing like >asciiDoc http://www.methods.co.nz/asciidoc/ > might be more appropriated. The down side is t

Re: [fossil-users] ZIP files cannot be extracted using Archive Utility on Mac

2009-10-18 Thread D. Richard Hipp
On Oct 18, 2009, at 10:06 AM, Dmitry Chestnykh wrote: > Actually, there's a better way to do this -- if initialized using > > deflateInit2(&stream, Z_BEST_COMPRESSION, Z_DEFLATED, -MAX_WBITS, 8, > Z_DEFAULT_STRATEGY); > > then zlib produces correct deflate output for ZIP files -- we don't > need

Re: [fossil-users] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Rene de Zwart
> I'm not sure I understand your request. > > The creole parser uses the same link code as the fossil parser. If you use > > [[8ae201d843|Link to Ticket]] > > A link to the ticket will appear. The same with check in and other > artifacts. Any artifact id > prefix will be converted to an appropriat

[fossil-users] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Robert
I'm not sure I understand your request. The creole parser uses the same link code as the fossil parser. If you use [[8ae201d843|Link to Ticket]] A link to the ticket will appear. The same with check in and other artifacts. Any artifact id prefix will be converted to an appropriate link. For wik

Re: [fossil-users] ZIP files cannot be extracted using Archive Utility on Mac

2009-10-18 Thread Dmitry Chestnykh
Actually, there's a better way to do this -- if initialized using deflateInit2(&stream, Z_BEST_COMPRESSION, Z_DEFLATED, -MAX_WBITS, 8, Z_DEFAULT_STRATEGY); then zlib produces correct deflate output for ZIP files -- we don't need to skip 2 bytes at the beginning, and 4 bytes at the end. On 1

Re: [fossil-users] ZIP files cannot be extracted using Archive Utility on Mac

2009-10-18 Thread Dmitry Chestnykh
It seems I figured it out! zlib adds 4 bytes of Adler32 CRC to the end of the stream. If, like with the first 2 bytes of the stream, we skip it, then Archive Utility works, and Fossil produces the same ZIP file as zip utility. Most likely other compression utilities just ignore Adler32 (or m

[fossil-users] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Rene de Zwart
Would it be feasible and of value to amend the creole link command to look up tickets, check-ins and wiki? By way of [[fossil:TYPE:id|title]] and TYPE being 1) tkt ticket 2) ci check-in 3) wiki wikipage it is a bit verbose and not exportable to other creole parsers but it plays nice to the l

Re: [fossil-users] COMSPEC on Windows

2009-10-18 Thread D. Richard Hipp
On Oct 18, 2009, at 7:15 AM, Emil Totev wrote: > Hi > I am just starting to explore this nice piece of software. I like it > very much for now, however I encountered a strange behavior - I really > think it is a bug. > > I am using Windows XP and JPSoftware's TCC as a replacement for the > comman

Re: [fossil-users] ZIP files cannot be extracted using Archive Utility on Mac

2009-10-18 Thread D. Richard Hipp
On Oct 18, 2009, at 6:42 AM, Dmitry Chestnykh wrote: > Hello, > > Mac OS X's built-in Archive Utility (which is the default way to > extract archives by double-clicking them) > cannot extract ZIP files generated by Fossil. http://www.fossil-scm.org/fossil/tktview?name=923a912309 Curiously, the

Re: [fossil-users] ZIP files cannot be extracted using Archive Utility on Mac

2009-10-18 Thread Stephan Beal
On Sun, Oct 18, 2009 at 12:55 PM, Dmitry Chestnykh wrote: > * test-fossil.zip - made by `fossil test-filezip test-fossil.zip wiki.h` > * test-zip.zip - made by `zip -9 test-zip.zip wiki.h` > > In case anyone would like to compare them. i can open them on Linux (x86/32) using "Ark" and "File Rol

[fossil-users] COMSPEC on Windows

2009-10-18 Thread Emil Totev
Hi I am just starting to explore this nice piece of software. I like it very much for now, however I encountered a strange behavior - I really think it is a bug. I am using Windows XP and JPSoftware's TCC as a replacement for the command-line shell. By default it is installed in C:\Program Files\J

[fossil-users] ZIP files cannot be extracted using Archive Utility on Mac

2009-10-18 Thread Dmitry Chestnykh
Hello, Mac OS X's built-in Archive Utility (which is the default way to extract archives by double-clicking them) cannot extract ZIP files generated by Fossil. It shows "Error 1 - Operation Not Permitted". Command-line unzip utility can extract them. I'm tinkering with zip.c, but cannot gen