Re: [fossil-users] Resolving recurring settings conflict

2018-06-07 Thread Warren Young
On Jun 7, 2018, at 7:04 PM, Warren Young wrote: > > I’ve set .fossil-settings/allow-symlinks to 1 in one of my repositories, so > in order to avoid the complaint from Fossil about a conflict, I also say > “fossil unset allow-symlinks” in the checkout. There’s a related bug that I forgot to

Re: [fossil-users] style.css served with on settings conflict

2018-06-07 Thread Warren Young
On Jun 7, 2018, at 6:58 PM, Andy Goth wrote: > > how does the error logger know that its output will wind up inside CSS? Is there any kind of “context” object that gets passed through the page rendering logic? If so, the high-level code that generates the CSS can declare that the final

[fossil-users] Resolving recurring settings conflict

2018-06-07 Thread Warren Young
I’ve set .fossil-settings/allow-symlinks to 1 in one of my repositories, so in order to avoid the complaint from Fossil about a conflict, I also say “fossil unset allow-symlinks” in the checkout. All is fine until I say “fossil conf pull all” command, whereupon the local setting comes back.

Re: [fossil-users] style.css served with on settings conflict

2018-06-07 Thread Andy Goth
On 06/07/18 19:55, Warren Young wrote: The error prepended to web pages served by Fossil on settings conflicts is being prepended to the style.css file, causing the CSS to be considered invalid by Chrome, at least. This should be done on HTML output only. I had this same problem back when

[fossil-users] style.css served with on settings conflict

2018-06-07 Thread Warren Young
The error prepended to web pages served by Fossil on settings conflicts is being prepended to the style.css file, causing the CSS to be considered invalid by Chrome, at least. This should be done on HTML output only. ___ fossil-users mailing list

Re: [fossil-users] Show time...

2018-06-07 Thread bytevolcano
On Mon, 4 Jun 2018 03:43:19 +0200 Stephan Beal wrote: > On Mon, Jun 4, 2018, 03:33 Richard Hipp wrote: > > > On 6/3/18, Richard Hipp wrote: > > > > > > So, if anybody sees any last minute tidying up that we need to do... > > > > For example, on the front page > >

Re: [fossil-users] Show time...

2018-06-07 Thread bytevolcano
- Paleo - Jurassic - Diatom - Trilobyte Better yet, find a term begining with 'C' so that you can have the 'C Versioning System.' On Wed, 6 Jun 2018 21:26:22 -0400 Eduard wrote: > I might enable public registration 'soon'. Now all I need is a catchy > name, like `chiselapp` :p

Re: [fossil-users] Compressed >>> uncompressed size

2018-06-07 Thread Andy Goth
32-bit Linux, no custom modifications, Fossil version e80667191a, self-compiled, ok. 5913941|3836467 5800401|3765158 3670410|3369067 3957878|3035526 3952468|3029402 3951235|2969330 3923360|2946572 4234202|2663321 5772779|2435585 3459064|2370320 I count 243 rows where length(content)>size, and

Re: [fossil-users] Show time...

2018-06-07 Thread Warren Young
On Jun 6, 2018, at 7:26 PM, Eduard wrote: > > Now all I need is a catchy name, like `chiselapp` :p I put my fossils in /museum. You are free to do the same. :) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Compressed >>> uncompressed size

2018-06-07 Thread Richard Hipp
On 6/7/18, Andy Goth wrote: > > I'm just going to go ahead and attach > the file. Very peculiar output. What platform is this running on? Have you made any modifications? Did you compile Fossil yourself? Try this: fossil sql "pragma integrity_check" If that returns "ok", then try

Re: [fossil-users] Compressed >>> uncompressed size

2018-06-07 Thread Andy Goth
On 06/07/18 14:00, Andy Goth wrote: On 06/07/18 08:51, Richard Hipp wrote: On 6/7/18, Andy Goth wrote: In a couple of my repositories (sorry, I can't share them), /artifact_stats shows artifact compressed sizes far larger than uncompressed sizes. Can you send the HTML generated by

Re: [fossil-users] Compressed >>> uncompressed size

2018-06-07 Thread Richard Hipp
On 6/7/18, Andy Goth wrote: > In a couple of my repositories (sorry, I can't share them), > /artifact_stats shows artifact compressed sizes far larger than > uncompressed sizes. Can you send the HTML generated by /artifact_stats? -- D. Richard Hipp d...@sqlite.org