[fossil-users] users table photo column

You may remember reading a few weeks back I've been playing around with putting together some "management" web management scaffolding around my repos to automate certain things (like copying "shared settings" from one repo to another, because I'm OCD like that, and not all config appear to have "gl

Re: [fossil-users] users table photo column

On Tue, May 27, 2014 at 4:05 AM, Scott Robison wrote: > You may remember reading a few weeks back I've been playing around with > putting together some "management" web management scaffolding around my > repos to automate certain things (like copying "shared settings" from one > repo to another, b

Re: [fossil-users] users table photo column

On Tue, May 27, 2014 at 4:22 AM, Richard Hipp wrote: > In any case, in the process I was looking at schema and saw there is a >> "photo" column in the users table. I imagine it is for a photo of the user, >> but cannot find anywhere that it is used. Is this something that was added >> for specifi

[fossil-users] Running script on push

Hi, Nowadays tools like Jenkins can run tests on triggers (or hooks), and it works wonderful. But Jenkins is overkilling (Java based :s) to be a match to the tiny but powerful and agile fossil. Even when this fellow ronperrela did a nice job integrating Jenkins: http://ronperrella.blogspot.com/20

Re: [fossil-users] Running script on push

I see there is a way to run a TH1 script. But as far as I see the th1 documentation, I can't find a way to invoke a shell script out of it. Any ideas??? 2014-05-27 8:04 GMT-04:30 Abilio Marques : > Hi, > > Nowadays tools like Jenkins can run tests on triggers (or hooks), and it > works wonderful

Re: [fossil-users] Running script on push

Thus said Abilio Marques on Tue, 27 May 2014 08:45:08 -0430: > I see there is a way to run a TH1 script. But as far as I see the th1 > documentation, I can't find a way to invoke a shell script out of it. > Any ideas??? Not sure if this is the best way, but while I was poking around in the TH

[fossil-users] FYI: doc URLs don't work with filenames that have + in their names

I had a file called README-Visual-C++.txt in one of my repositories and wanted to link to the tip version of it from an outside web page. I discovered the "doc URL" feature in Fossil, but it didn't work with that file. Apparently there's some kind of data sanitization going on here that turns

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

On Tue, May 27, 2014 at 3:43 PM, Warren Young wrote: > I had a file called README-Visual-C++.txt in one of my repositories and > wanted to link to the tip version of it from an outside web page. I > discovered the "doc URL" feature in Fossil, but it didn't work with that > file. Apparently ther

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

Thus said Richard Hipp on Tue, 27 May 2014 15:46:30 -0400: > I think that's an HTTP thing. In a URL, spaces are encoded as "+". So > fossil is doing the right thing in converting "+" characters in the > URL into spaces. It certainly handles them correctly when given them, however, there may

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

Or, maybe $current_page should be HTTP-encoded instead of plaintext. On Tue, May 27, 2014 at 4:19 PM, Andy Bradford wrote: > Thus said Richard Hipp on Tue, 27 May 2014 15:46:30 -0400: > > > I think that's an HTTP thing. In a URL, spaces are encoded as "+". So > > fossil is doing the right thin

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

Candidate fix checked into trunk. On Tue, May 27, 2014 at 4:21 PM, Richard Hipp wrote: > Or, maybe $current_page should be HTTP-encoded instead of plaintext. > > > On Tue, May 27, 2014 at 4:19 PM, Andy Bradford > wrote: > >> Thus said Richard Hipp on Tue, 27 May 2014 15:46:30 -0400: >> >> > I

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

Hello, on Tuesday 27 May 2014 at 15:46, Richard Hipp wrote: > On Tue, May 27, 2014 at 3:43 PM, Warren Young wrote: > > > I had a file called README-Visual-C++.txt in one of my repositories and > > wanted to link to the tip version of it from an outside web page. I > > discovered the "doc URL" f

[fossil-users] Server static files to load JSON APP

Hi fossil-users, I have simple JS app (build with GWT) and these static files are in one folder ./jsout How can I start fossil to serve these files in static mode. I need a comand like that: ./fossil server repo.db --static-dir ./jsout --static-url /jsout And http://localhost:8080/jsout/inde

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

On 5/27/2014 13:46, Richard Hipp wrote: If the filename really does contain "+" symbols, then the URL should have "%2b" for each plus. Sorry, I should have mentioned that I did try that. This is with the nginx-proxied configuration that I posted here about on Sunday. I suspect nginx is tran

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

On 5/27/2014 14:37, Richard Hipp wrote: Candidate fix checked into trunk. I just installed [5d4400400a] and it still doesn't work, regardless of %2b or not %2b. (That *was* the query, quoth Hamlet after all.) I get a "Document Not Found" page back from Fossil, with the body section being "

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

On May 27, 2014 6:58 PM, "Warren Young" wrote: > Incidentally, I'm bothering with nginx proxying because the SCGI method seems to have broken in 1.28. It was working fine on my site with 1.27 from the Ubuntu repository until I upgraded to 1.28 by building from source. (I wanted the /tree featur

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

On 5/27/2014 17:10, Joe Prostko wrote: On May 27, 2014 6:58 PM, "Warren Young" mailto:war...@etr-usa.com>> wrote: > Incidentally, I'm bothering with nginx proxying because the SCGI method seems to have broken in 1.28. It was working fine on my site with 1.27 from the Ubuntu repository until I

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

Is the documentation better now? http://www.fossil-scm.org/fossil/doc/trunk/www/server.wiki#scgi Thanks for testing out SCGI for us. On Tue, May 27, 2014 at 7:31 PM, Warren Young wrote: > On 5/27/2014 17:10, Joe Prostko wrote: > >> On May 27, 2014 6:58 PM, "Warren Young" >

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

On 5/27/2014 17:41, Richard Hipp wrote: Is the documentation better now? Yes, 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] FYI: doc URLs don't work with filenames that have + in their names

On 5/27/2014 17:48, Warren Young wrote: On 5/27/2014 17:41, Richard Hipp wrote: Is the documentation better now? Yes, thanks! Ooops, grammar bug: "Add one might want..." Do you mean "Additionally, ..."? ___ fossil-users mailing list fossil-users@

[fossil-users] git export bug, and fix.

Using the fossil head, i.e. This is fossil version 1.29 [5d4400400a] 2014-05-27 20:36:33 UTC for a git export on my clone of http://core.tcl.tk/akupries/fx/home I.e. fossil export --git > DUMP the resulting DUMP contains lines of the form: % grep -n ^committer DUMP| head 229901:comm

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

Thus said Richard Hipp on Tue, 27 May 2014 16:37:01 -0400: > Candidate fix checked into trunk. Works here, and much nicer than what I suggested: Before: $ printf 'GET /doc/tip/test/test-page%%2b%%2b.wiki HTTP/1.1\r\nHost: localhost:8080\r\n\r\n' | nc localhost 8080 | grep base http://localhost

Re: [fossil-users] git export bug, and fix.

Are you planning to check your changes in? On Tue, May 27, 2014 at 7:55 PM, Andreas Kupries wrote: > Using the fossil head, i.e. > This is fossil version 1.29 [5d4400400a] 2014-05-27 20:36:33 UTC > > for a git export on my clone of > http://core.tcl.tk/akupries/fx/home > > I.e. > fos

Re: [fossil-users] git export bug, and fix.

I can do that. Note that I am about to go home and would do the commit after my arrival there, which should be in about 2 hours (*). (*) Normally 1/2 hour, however nowadays I try to walk a bit longer for exercise. On Tue, May 27, 2014 at 5:20 PM, Richard Hipp wrote: > Are you planning to check y

Re: [fossil-users] git export bug, and fix.

On Tue, May 27, 2014 at 8:26 PM, Andreas Kupries wrote: > I can do that. Note that I am about to go home and would do the commit > after my arrival there, which should be in about 2 hours (*). > We await your fix. -- D. Richard Hipp d...@sqlite.org ___

Re: [fossil-users] git export bug, and fix.

Ok. On Tue, May 27, 2014 at 5:28 PM, Richard Hipp wrote: > On Tue, May 27, 2014 at 8:26 PM, Andreas Kupries > wrote: >> >> I can do that. Note that I am about to go home and would do the commit >> after my arrival there, which should be in about 2 hours (*). > > > We await your fix. > -- > D. Ri

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

On Tue, May 27, 2014 at 11:31 PM, Warren Young wrote: > On 5/27/2014 17:10, Joe Prostko wrote: >> >> On May 27, 2014 6:58 PM, "Warren Young" > > wrote: >> >> > Incidentally, I'm bothering with nginx proxying because the SCGI >> method seems to have broken in 1.28. It w

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

Richard Hipp wrote: I think that's an HTTP thing. In a URL, spaces are encoded as "+". So fossil is doing the right thing in converting "+" characters in the URL into spaces. If the filename really does contain "+" symbols, then the URL should have "%2b" for each plus. ex: http://localhos

Re: [fossil-users] FYI: doc URLs don't work with filenames that have + in their names

Thus said Joel Bruick on Tue, 27 May 2014 21:55:06 -0400: > It's really an HTML form thing [1] that only applies to the query > portion of the URL. In the path component, we technically should be > percent-encoding spaces and leaving any instances of "+" alone, which > would then allow yo

Re: [fossil-users] git export bug, and fix.

And done. See http://fossil-scm.org/index.html/info/de1921bad3ce6b0a25d654b993fe3fc768139162 On Tue, May 27, 2014 at 5:29 PM, Andreas Kupries wrote: > Ok. > > On Tue, May 27, 2014 at 5:28 PM, Richard Hipp wrote: >> On Tue, May 27, 2014 at 8:26 PM, Andreas Kupries >> wrote: >>> >>> I can do

[fossil-users] Markdown

Is there a "definitive list" of what is and is not supported by the markdown engine within fossil WRT repo relative links? Other than reading the code, that is? The best I can come up with for a link to a wiki page (from another wiki page) is something like "[Page](wiki?name=Page)" which really see