Re: [fossil-users] Automatic creation of file to wiki or embedded docs
On Tue, Jan 18, 2011 at 11:26 AM, Stephan Beal sgb...@googlemail.comwrote: i hadn't considered that approach - i'll have to try that out. i can think of no reason that that shouldn't work. A quick check shows that those files get processed by fossil, as well, or my browser downloads them instead of displaying them, so this won't work for what i was trying to do. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ 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] Automatic creation of file to wiki or embedded docs
On Tue, 18 Jan 2011 09:25:09 +, David Bovill wrote:
Thanks for the comments Rene...
On 17 January 2011 23:50, Rene wrote:
You can link to the source code file. But the source code file
cannot
link to the documentation.
It could do with a minor tweak to the template for the file info page
:) It's a basic UX feature - you go from docs to source code but
can't
get back :(
All the templates fossil is using are under Admin (header,
footer,
[skins, css]) and you can change them as much as you want.
I've been trying these, and they are great. I'm not sure I can use
them to create conditional links from the file section to the
documentation section - it may be possible using TH1 / and / or some
Javascript.
I've read the TH1 pdf, and it covers the basic language well. I'm
wandering what access we have to Fossil variables - page title,
section type etc that may be available to use in the language?
Can anyone help with posting a TH1 snippet that would detect if a
user was in a particular section - say the file-info page?
It is important to understand that
th1 is server-side processing
javascript is client-side processing e.g. Your browser
I checked and in style.c these are axported to TH 1:
/* Generate the header up through the main menu */
Th_Store(project_name, db_get(project-name,Unnamed Fossil
Project));
Th_Store(title, zTitle);
Th_Store(baseurl, g.zBaseURL);
Th_Store(home, g.zTop);
Th_Store(index_page, db_get(index-page,/home));
Th_Store(current_page, g.zPath);
Th_Store(manifest_version, MANIFEST_VERSION);
Th_Store(manifest_date, MANIFEST_DATE);
Th_Store(compiler_name, COMPILER_NAME);
if( g.zLogin ){
Th_Store(login, g.zLogin);
}
you can check if $current_page == finfo. But you miss the arguments to
finfo.
in g(lobal) are these 3 defined
char *zPath;/* Name of webpage being served */
char *zExtra; /* Extra path information past the webpage
name */
char *zBaseURL; /* Full text of the URL being served */
zExtra (I assume) contains the name=arg. But it isn't made available in
th1. So you cannot
generate a link to the documentation.
Bummer. You could ask if richard want to add something like:
Th_Store(parameters, g.zExtra);
--
Rene
___
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] Automatic creation of file to wiki or embedded docs
Very useful Rene!
Thanks :) And Richard do please add Th_Store(parameters, g.zExtra) :)
On 18 January 2011 13:14, Rene renew...@xs4all.nl wrote:
On Tue, 18 Jan 2011 09:25:09 +, David Bovill wrote:
Thanks for the comments Rene...
On 17 January 2011 23:50, Rene wrote:
You can link to the source code file. But the source code file
cannot
link to the documentation.
It could do with a minor tweak to the template for the file info page
:) It's a basic UX feature - you go from docs to source code but
can't
get back :(
All the templates fossil is using are under Admin (header,
footer,
[skins, css]) and you can change them as much as you want.
I've been trying these, and they are great. I'm not sure I can use
them to create conditional links from the file section to the
documentation section - it may be possible using TH1 / and / or some
Javascript.
I've read the TH1 pdf, and it covers the basic language well. I'm
wandering what access we have to Fossil variables - page title,
section type etc that may be available to use in the language?
Can anyone help with posting a TH1 snippet that would detect if a
user was in a particular section - say the file-info page?
It is important to understand that
th1 is server-side processing
javascript is client-side processing e.g. Your browser
I checked and in style.c these are axported to TH 1:
/* Generate the header up through the main menu */
Th_Store(project_name, db_get(project-name,Unnamed Fossil
Project));
Th_Store(title, zTitle);
Th_Store(baseurl, g.zBaseURL);
Th_Store(home, g.zTop);
Th_Store(index_page, db_get(index-page,/home));
Th_Store(current_page, g.zPath);
Th_Store(manifest_version, MANIFEST_VERSION);
Th_Store(manifest_date, MANIFEST_DATE);
Th_Store(compiler_name, COMPILER_NAME);
if( g.zLogin ){
Th_Store(login, g.zLogin);
}
you can check if $current_page == finfo. But you miss the arguments to
finfo.
in g(lobal) are these 3 defined
char *zPath;/* Name of webpage being served */
char *zExtra; /* Extra path information past the webpage
name */
char *zBaseURL; /* Full text of the URL being served */
zExtra (I assume) contains the name=arg. But it isn't made available in
th1. So you cannot
generate a link to the documentation.
Bummer. You could ask if richard want to add something like:
Th_Store(parameters, g.zExtra);
--
Rene
___
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
[fossil-users] Is there a way to synchronize two repositories on a same file system without having to run a server?
In my daily work I make a backup of a repository every day. Copying the file takes much time and often it's faster to do: fossil server /path/to/backup and in another console: fossil remote-url http://localhost:8080 fossil sync fossil remote-url off However I would really appreciate if there was a way of synchronizing my two repositories as a native function. Maybe this could be transformed into an SQLite question because it was originally a copy, has therefore the same user, shunning list, configuration and other non-push/pulled information. The SQLite question would then be: how to backup a database efficiently given that we know the names of the tables of which the content is evergrowing. Thank you for your insights, Benoit -- Benoit Mortgat 20, avenue Marcel Paul 69200 Vénissieux, France +33 6 17 15 41 58 +33 4 27 11 61 23 ___ 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] Is there a way to synchronize two repositories on a same file system without having to run a server?
On Tue, Jan 18, 2011 at 04:40:15PM +0100, Benoit Mortgat wrote: However I would really appreciate if there was a way of synchronizing my two repositories as a native function. fossil pull -R backup.fossil /path/to/orig.fossil Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Why can nobody checkout but not clone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've used Fossil on various open source projects, and keep discovering that I need to permit the nobody user to clone these repositories--this, despite the fact that it has the checkout permission by default. When might one have the checkout permission and not the clone permission? What is the reasoning for giving the nobody user the former and not the latter by default? Thanks. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk013pUACgkQIaMjFWMehWJF+QCeMLSsK7umEow+ybaLXrLY2RMq n3gAn2IJtaT03TRk2Sge8RJogpX/3f/C =6T7m -END PGP SIGNATURE- ___ 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] Why can nobody checkout but not clone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ah, OK, if it's fixed then awesome. This particular project was converted from Git a couple months back, so perhaps it was done without the fixed Fossil and got the old permissions. Though I still wonder what's the justification for making Clone a separate permission. I mean, what's the point of checking out if you can't clone in the first place, or cloning if you can't check out to update that clone later? On 01/18/2011 01:26 PM, Joerg Sonnenberger wrote: On Tue, Jan 18, 2011 at 12:40:21PM -0600, Nolan Darilek wrote: I've used Fossil on various open source projects, and keep discovering that I need to permit the nobody user to clone these repositories--this, despite the fact that it has the checkout permission by default. How recent is your fossil? I remember some change for exactly this issue a while ago. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0167oACgkQIaMjFWMehWL/sACfXfpLU+QCmE/+obBDfNmKQt2/ /sMAmweUZD0GiCyYpLaQP0O+vL9wkAGm =xZge -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
