Re: [fossil-users] TortoiseFossil to BSD license

Hi Rüdiger, I'll try to get an alpha out soon after I've improved the caching, it will need to be installed manually though unless I find time to make an installer by then. Thanks, Edward Blake --- r_haer...@gmx.de wrote: Hello Edward, can you send me precompiled tortoise-fossil? Regards Rüd

Re: [fossil-users] My report-writing utility for ticket summaries

On 2/8/2013 4:07 PM, Stephan Beal wrote: Please forgive my ignorance of lua, but what am i missing here? Sorry, I should have included a list of prerequisite Lua modules. On Windows, all the prerequisites (and lots more modules) are satisfied by the Lua for Windows distribution avai

Re: [fossil-users] My report-writing utility for ticket summaries

On 2/8/2013 4:16 PM, David Given wrote: On 09/02/13 00:07, Stephan Beal wrote: [...] Please forgive my ignorance of lua, but what am i missing here? [stephan@host:~/cvs/fossil/ticketer/reporter]$ lua reporter.lua lua: reporter.lua:62: module 'pl.path' not found: [...] i can't seem to find any

Re: [fossil-users] My report-writing utility for ticket summaries

On 09/02/13 00:07, Stephan Beal wrote: [...] > Please forgive my ignorance of lua, but what am i missing here? > > [stephan@host:~/cvs/fossil/ticketer/reporter]$ lua reporter.lua > lua: reporter.lua:62: module 'pl.path' not found: [...] > i can't seem to find any "pl" module in my package db (Ubu

Re: [fossil-users] My report-writing utility for ticket summaries

On Sat, Feb 9, 2013 at 12:59 AM, Ross Berteig wrote: > https://chiselapp.com/user/**rberteig/repository/Ticketer/**home Please forgive my ignorance of lua, but what am i missing here? [stephan@host:~/cvs/fossil/ticketer/reporter]$ l

[fossil-users] My report-writing utility for ticket summaries

I promised to share this utility recently. If I had my druthers, I'd hold off until it was "finished" and "ready for public use". But we all know how that goes. So, I've cloned and published the repository I keep for documenting my understanding of the ticket system that happens to contain my r

Re: [fossil-users] 101 entries... when it should be 200...

On Fri, Feb 8, 2013 at 4:37 PM, K. Fossil user < ticketpersonnal-fos...@yahoo.fr> wrote: > 1/ I agree with the 20-200, but my idea is this : > I would like to know which button I've pressed: 200 or 20 ? (it doesn't > matter if n=100) > That assumes that the C code knows exactly which menu entries

Re: [fossil-users] 101 entries... when it should be 200...

1/ I agree with the 20-200, but my idea is this : I would like to know which button I've pressed: 200 or 20 ? (it doesn't matter if n=100) Never mind, this is not that important for me. It could be that important for some people... 2/ The timeline variant is strange, because I've thought that if

Re: [fossil-users] 101 entries... when it should be 200...

On Fri, Feb 8, 2013 at 3:45 PM, K. Fossil user < ticketpersonnal-fos...@yahoo.fr> wrote: > 2/ Is it possible that you put a tooltip when the mouse is hovering ? > (at most 200 entries, for example) > That is unfortunately a bigger change that it might initially seem because those menus are create

Re: [fossil-users] 101 entries... when it should be 200...

On Fri, Feb 8, 2013 at 3:39 PM, K. Fossil user < ticketpersonnal-fos...@yahoo.fr> wrote: > 1/ else does not break here... :-) > It runs as expected... > (if entries are over 20 then 20) > Try this: http://fossil-scm.org/index.html/timeline?n=100 With the "else", the "200" entry would not appear

Re: [fossil-users] 101 entries... when it should be 200...

1/ at most 200 entries Ah ok... 2/ Is it possible that you put a tooltip when the mouse is hovering ? (at most 200 entries, for example) 3/ Thanks for the b=trunk... I was wondering *if* it should not be b=trunk then...   Best Regards K. Richard Hipp wrote : On Fri, Feb 8, 2013 at 8:44 AM

Re: [fossil-users] 101 entries... when it should be 200...

1/ else does not break here... :-) It runs as expected... (if entries are over 20 then 20) 2/ Depending on the trunk I click on, it may say 14 or 15 or 11... 14 timeline items related to "trunk" occurring around 2013-02-07 15:28:18   Best Regards K. De : St

Re: [fossil-users] 101 entries... when it should be 200...

On Fri, Feb 8, 2013 at 3:14 PM, K. Fossil user < ticketpersonnal-fos...@yahoo.fr> wrote: > 1/ it is the fossil repository... :-) > Doh. > 2/ may be this can solve it ? > File is : src/timeline.c > line 1359, change it to : > else if( nEntry<200 ){ > An else there would break if (nEntry>2

Re: [fossil-users] 101 entries... when it should be 200...

On Fri, Feb 8, 2013 at 8:44 AM, K. Fossil user < ticketpersonnal-fos...@yahoo.fr> wrote: > Hello again, > > Click on "Timeline" > then click on "tags: trunk" > finally click on button "200 entries" > That button really means "at most 200 entries" but that is too much text for a button, so it is a

Re: [fossil-users] 101 entries... when it should be 200...

1/ it is the fossil repository... :-) $ fossil dbstat repository-size:    40726528 bytes (40.7MB) artifact-count: 19750 (stored as 5624 full text and 14126 delta blobs) artifact-sizes: 52103 bytes average, 4993770 bytes max, 1028938476 bytes (1.0GB) total compression-ratio:  25:1 checki

Re: [fossil-users] 101 entries... when it should be 200...

On Fri, Feb 8, 2013 at 2:44 PM, K. Fossil user < ticketpersonnal-fos...@yahoo.fr> wrote: > I can read 101 entries... when it should be 200... > Two buttons appear [20 entries], which is correct and [200 entries] that > should not exists... > Does your repo have more than 101 entries? What does t

[fossil-users] 101 entries... when it should be 200...

Hello again, Click on "Timeline" then click on "tags: trunk" finally click on button "200 entries" I can read 101 entries... when it should be 200... Two buttons appear [20 entries], which is correct and [200 entries] that should not exists... date in the bottom is 2013-01-03 22:33   Best Reg

[fossil-users] CORS requests and the JSON API?

I should clarify a bit Stephan -- it was not specifically a doubled Access-Control-Allow-Origin header that destroyed my week but rather was a doubled Content-Length header. I was in the same boat as you though. If I explicitly added it it was doubled, and if not it wasn't correct (on that server c

Re: [fossil-users] CORS requests and the JSON API?

On Fri, Feb 8, 2013 at 2:26 AM, Themba Fletcher wrote: > Whoops -- please ignore the previous stuff for now. > > You have a doubled "Access-Control-Allow-Origin" header in your response: > i saw that but "it's not my fault" - if i don't configure Apache to send this header then it does not. If i

Re: [fossil-users] CORS requests and the JSON API?

On Fri, Feb 8, 2013 at 2:23 AM, Themba Fletcher wrote: > If I understand correctly the OPTIONS request is forced by the fact that > your POST's content-type is application/json > -- Any request that's not a Simple Request gets a preflight because the > W3C says so. Simple requests are defined as (