Re: [fossil-users] How to enable TH1?

2015-06-28 Thread lz
Try 
http://www.eurotcl.tcl3d.org/eurotcl-2012/presentations/01-Hipp-Fossil.odp


On 06/28/2015 03:06 AM, Michael Richter wrote:
On 27 June 2015 at 01:06, Joe Mistachkin sql...@mistachkin.com 
mailto:sql...@mistachkin.com wrote:


This must be enabled at compile-time as well via the
FOSSIL_ENABLE_TH1_DOCS
define.  When using ./configure, you can specify:

--with-th1-docs=1


What, exactly, does this actually do?  I can't find any information on 
this whatsoever.


--
Perhaps people don't believe this, but throughout all of the 
discussions of entering China our focus has really been what's best 
for the Chinese people. It's not been about our revenue or profit or 
whatnot.

--Sergey Brin, demonstrating the emptiness of the don't be evil mantra.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
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] fossil serve repolist error

2015-06-28 Thread Richard Hipp
On 6/28/15, Remco Schoen remco_sch...@me.com wrote:

 Finally found some time to test and react. The webserver now “freezes” when
 trying to open the repolist, like the request never is closed from the
 server side. The process takes 100% CPU then.


The way to debug this is to compile Fossil with -O0 and -g and then
run it inside of gdb.  Create a file request.txt that say:

GET /\n\n

That is, a line of GET / followed by a blank line.  Then run:

 run http --repolist /path/to/directory request.txt

Maybe set a breakpoint on process_one_web_page and single-step from
there.  Or let it run in its loop for a while and then interrupt with
Ctrl-C and do bt for a stack trace to try to figure out what is
going wrong that way.

-- 
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


[fossil-users] Seeking feedback on the rssTags branch...

2015-06-28 Thread Joe Mistachkin

I wanted the ability to see the associated branch for each RSS item on a
Fossil feed, so I made the necessary modifications on a branch.  I think
the (quite minor) changes are merge-worthy at this point.

Any objections?  Other feedback?

--
Joe Mistachkin

___
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] fossil serve repolist error

2015-06-28 Thread Remco Schoen

 Op 27 jun. 2015, om 23:48 heeft Richard Hipp d...@sqlite.org het volgende 
 geschreven:
 
 I found out, that it never reaches that code. It doesn’t pass this check as
 the size of .fossil is larger then 1024. So apparently it already attached
 .fossil to the folder path and is trying to use it as a repository.
 
  if( szFile1024 ){
set_base_url(0);
if( strcmp(zPathInfo,/)==0
   allowRepoList
   repo_list_page() ){
 
 
 Thanks of the analysis.  Problems should now be fixed on trunk.

Finally found some time to test and react. The webserver now “freezes” when 
trying to open the repolist, like the request never is closed from the server 
side. The process takes 100% CPU then.

Kind regards,

Remco Schoen___
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] How to enable TH1?

2015-06-28 Thread Joe Mistachkin

Michael Richter wrote:
 
 What, exactly, does this actually do?  I can't find any information on
this
 whatsoever.


Technically, it is documented in the help for the settings command.

I suppose that I should provide more details on the primary TH1 integration
reference page:

https://www.fossil-scm.org/fossil/doc/trunk/www/th1.md

My conference slides describing how to use this feature (and other Tcl
integration features) are here:

http://eagle.to/tcl2014/fossil-tcl.pdf

Here is the relevant excerpt from the help for the settings command:

   tcl  If enabled (and Fossil was compiled with Tcl support),
Tcl integration commands will be added to the TH1
interpreter, allowing arbitrary Tcl expressions and
scripts to be evaluated from TH1.  Additionally, the Tcl
interpreter will be able to evaluate arbitrary TH1
expressions and scripts. Default: off.

   tcl-setupThis is the setup script to be evaluated after creating
(versionable)   and initializing the Tcl interpreter.  By default, this
is empty and no extra setup is performed.

   th1-docs WARNING: If enabled (and Fossil was compiled with TH1
support for embedded documentation files), this allows
embedded documentation files to contain arbitrary TH1
scripts that are evaluated on the server.  If native
Tcl integration is also enabled, this setting has the
potential to allow anybody with check-in privileges to
do almost anything that the associated operating system
user account could do.  Extreme caution should be used
when enabling this setting.  Default: off.

   th1-hooksIf enabled (and Fossil was compiled with support for TH1
hooks), special TH1 commands will be called before and
after any Fossil command or web page. Default: off.

   th1-setupThis is the setup script to be evaluated after creating
(versionable)   and initializing the TH1 interpreter.  By default, this
is empty and no extra setup is performed.

   th1-uri-regexp   Specify which URI's are allowed in HTTP requests from
(versionable)   TH1 scripts.  If empty, no HTTP requests are allowed
whatsoever.  The default is an empty string.

--
Joe Mistachkin

___
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] Seeking feedback on the rssTags branch...

2015-06-28 Thread jungle Boogie
Hi Joe,
On Jun 28, 2015 11:20 AM, Joe Mistachkin sql...@mistachkin.com wrote:


 I wanted the ability to see the associated branch for each RSS item on a
 Fossil feed, so I made the necessary modifications on a branch.  I think
 the (quite minor) changes are merge-worthy at this point.

 Any objections?  Other feedback?


I like it. Thank you!
Now someone can know tags without also looking at each commit. This may not
be that big of an issue with the fossil code, but I see it benefiting
sqlite repo quite well and of course repos with many tags/branches.

 --
 Joe Mistachkin


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users