[fossil-users] Bug: Ticket formatting breaks if you enable HTML as wiki markup language

[Roy Keene]

There is a bug in Fossil (v2.2) that breaks the formatting of tickets if 
you enable the Configuration option "Use HTML as wiki markup language".


With this option off, tickets get formatted correctly, like:
	Debugging information taken at the time the 
issue was on-going:


With this option on, tickets get formatted incorrectly, like:
	Debugging information taken at the 
time the issue was on-going:


From a quick look at the source it looks like the ticket formatting system 
ONLY outputs Fossil Wiki and relies upon the Fossil Wiki formatting engine 
to be aware of these weird formatting rules and translate them into HTML, 
but enabling "Use HTML as wiki markup language" disables that.

___
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] Blockquotes end up in code/pre blocks

[Chris Rydalch]

That works, thanks Richard!

On Wed, Jun 7, 2017 at 12:06 PM, Richard Hipp  wrote:

> On 6/7/17, Chris Rydalch  wrote:
> > When I put code formatted like this into a wiki page, block quotes are
> > detected and inserted into the code.
>
> Maybe use the special ... tags around your code?
>
> --
> 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Blockquotes end up in code/pre blocks

[Richard Hipp]

On 6/7/17, Chris Rydalch  wrote:
> When I put code formatted like this into a wiki page, block quotes are
> detected and inserted into the code.

Maybe use the special ... tags around your code?

-- 
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] Blockquotes end up in code/pre blocks

[Chris Rydalch]

When I put code formatted like this into a wiki page, block quotes are
detected and inserted into the code. For example, put this code in a wiki
page:


// Grow Hairs
vector dir = { 0, 1, 0 };
// dir = @N;// grow in normal direction
float len = 1.0;
int   steps = 10;
float jitter = 0.1;
float seed = 0.12345;

vector  pos = @P;
int pr = addprim(geoself(), "polyline");

// Start the curve with our point
addvertex(geoself(), pr, @ptnum);
for (int i = 0; i < steps; i++)
{
pos += dir * len / steps;
pos += (vector(rand( @ptnum + seed )) - 0.5) * jitter;

// Clone our point to copy attributes
int pt = addpoint(geoself(), @ptnum);
// But write a new position
setpointattrib(geoself(), "P", pt, pos);

// Connect the new point to our curve.
addvertex(geoself(), pr, pt);
seed += $PI;
}


Block quotes end up inside the for loop when the wiki page is
previewed/saved. Here is the generated HTML:


// Grow Hairs
vector dir = { 0, 1, 0 };
// dir = @N;// grow in normal direction
float len = 1.0;
int   steps = 10;
float jitter = 0.1;
float seed = 0.12345;
vector  pos = @P;
int pr = addprim(geoself(), "polyline");
// Start the curve with our point
addvertex(geoself(), pr, @ptnum);
for (int i = 0; i  steps; i++)
{
pos += dir * len / steps;
pos += (vector(rand( @ptnum + seed )) - 0.5) * jitter;
// Clone our point to copy attributes
int pt = addpoint(geoself(), @ptnum);
// But write a new position
setpointattrib(geoself(), "P", pt, pos);

// Connect the new point to our curve.
addvertex(geoself(), pr, pt);
seed += $PI;
}


Is this a bug? Also, should the paragraph tags not end up inside pre/code
as well?

Thanks!

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

[fossil-users] Improvements to the /reports page

[Roy Keene]

All,

	I would benefit from some improvements to the /reports page, such 
as the ability to restrict the dates upon which are being reported and the 
ability to restrict the report to certain tags.


I've started on the former change here:

https://chiselapp.com/user/rkeene/repository/fossil/vdiff?from=6419592d65=stats-with-date-boundaries=0

Let me know if this has a chance of being improved and merged upstream and 
I'll work on improving it and adding more functionality.


Thanks,
Roy Keene
___
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 JSON API: How to create a wiki page?

[Stephan Beal]

Patches are welcomed :-D


- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.

On Jun 7, 2017 15:55, "Warren Young"  wrote:

On Jun 7, 2017, at 7:38 AM, Stephan Beal  wrote:
>
> BTW- there is an API intended just for checking whether json is built in:
/json/HAI (from lolcatz jargon... it made sense at the time (2011)).

Then I have a new bug to file: it doesn’t respond KTHXBYE as it obviously
should.

http://www.lolcode.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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] "fossil http" doubts

[Johan Kuuse]

On Wed, Jun 7, 2017 at 3:50 PM, Warren Young  wrote:
> On Jun 7, 2017, at 7:42 AM, Johan Kuuse  wrote:
>>
>> 2. I want to validate the web pages: Validate the HTML, check for
>> broken links, etc, using for example the W3C validation tools.
>
> If you’re using something like curl or wget to pull the web pages, there’s 
> typically a way to set up a “cookie jar” so that you can log in with one HTTP 
> request, then make the remaining HTTP requests as that user, with the HTTP 
> client automatically sending the necessary session cookie.


Thanks for the suggestion, but I wanted to avoid both a running web
server and the cookie jar setup.
"fossil test-http" made my day.
Get the HTML (including the HTTP Response header) from all Fossil
built-in web pages, using the output from 'fossil help -w' as a list:

mkdir -p fhtml && for w in `fossil help -w | xargs printf "%s\n"`; do
printf "GET $w HTTP/1.0\n\n" | fossil test-http > fhtml/${w}.html;done

BR,
Johan
___
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 JSON API: How to create a wiki page?

[Warren Young]

On Jun 7, 2017, at 7:38 AM, Stephan Beal  wrote:
> 
> BTW- there is an API intended just for checking whether json is built in: 
> /json/HAI (from lolcatz jargon... it made sense at the time (2011)).

Then I have a new bug to file: it doesn’t respond KTHXBYE as it obviously 
should.

http://www.lolcode.org/
___
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 http" doubts

[Warren Young]

On Jun 7, 2017, at 7:42 AM, Johan Kuuse  wrote:
> 
> 2. I want to validate the web pages: Validate the HTML, check for
> broken links, etc, using for example the W3C validation tools.

If you’re using something like curl or wget to pull the web pages, there’s 
typically a way to set up a “cookie jar” so that you can log in with one HTTP 
request, then make the remaining HTTP requests as that user, with the HTTP 
client automatically sending the necessary session cookie.
___
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 http" doubts

[Johan Kuuse]

Thanks for the input.
"fossil test-http" did the trick:

webpage=/setup
printf "GET $webpage HTTP/1.0\n\n" | fossil test-http

My purposes for parsing the built-in web pages are basically two:

1. I want to hack the Fossil code:
a. I parse and save the HTML from the builtin pages (excluding
pages where the output makes no sense, for example /zip)
b. I modify the source code (related to one or more web pages)
c. I parse the same pages again to check that I have changed only
the web page output I intended to change. A kind of self test before
committing.

This WoW is obviously only helpful for a developer changing the Fossil
source code of one single (official) commit.
It does not make sense to save the output for later use and compare it
between commits, as the content/structure may change.


2. I want to validate the web pages: Validate the HTML, check for
broken links, etc, using for example the W3C validation tools.

This kind of validation could be used both to find existing, and to
avoid introducing new invalid HTML.
Could possibly be useful both for programmers and for skin-makers.


BR,
Johan



On Wed, Jun 7, 2017 at 11:53 AM, Stephan Beal  wrote:
> On Wed, Jun 7, 2017 at 8:48 AM, Johan Kuuse  wrote:
>>
>> My idea is to make a script which parses the output from all builtin
>> pages.
>
>
> Be aware that fossil makes NO GUARANTEES about the stability of
> content/structure of any pages (or CLI command output, for that matter).
> Thus any work you do on parsing any pages might be undone by any given
> commit to the main fossil tree.
>
> --
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
> those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
>
> ___
> 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 JSON API: How to create a wiki page?

[Stephan Beal]

On Jun 7, 2017 03:59, "Warren Young"  wrote:

That’s a much simpler call.  It doesn’t require any permissions, and it’s a
GET call, not a POST call.  That test proves little other than that you
have a working JSON API in your local Fossil instance.


BTW- there is an API intended just for checking whether json is built in:
/json/HAI (from lolcatz jargon... it made sense at the time (2011)).
___
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 JSON API: How to create a wiki page?

[Offray Vladimir Luna Cárdenas]

Thanks Warren,

The problem was related with the curled quotes. Now is working fine.

The simpler test was because I was getting "

curl: (6) Could not resolve host:  -d

So I was interested in see the host resolution with a simpler command.

Cheers,

Offray

On 06/06/17 20:58, Warren Young wrote:
> On Jun 6, 2017, at 5:51 PM, Offray Vladimir Luna Cárdenas  
> wrote:
>> When I try something similar with:
>>
>> curl -H "Content-Type: application/json" \ -d '{"authToken":
>> "mytoken",\
>>"payload": {"name": “foo", "content": "bar"}}'
>> http://localhost:8081/json/wiki/create
> You’re missing a backslash between the JSON string and the URL.
>
> The backslashes are largely for formatting reasons, so that I could continue 
> a long command onto multiple lines in the email.  I recommend that you just 
> type this as a single command, not copy-paste it as shown in the email.
>
> Also, my mailer curled one of the quotes around “foo”, which you’ve copied 
> into your command, and that will break the JSON parser.  It needs to be an 
> ASCII double quote.
>
> (I try to catch it when this happens, but sometimes my mailer is smarter than 
> I am.)
>
>> but if I do:
>>
>> curl http://localhost:8081/json/wiki/timeline
>>
>> I get:
>>
>> {"fossil":"81d7d3f43ebd4e77095cfbacee7ebc9ae043a014760cde56d437dbd8b6a37c92","timestamp":1496792951,"command":"wiki/timeline","procTimeUs":,"procTimeMs":3,"payload":{"limit":20,"timeline":[]}}%
>>
>>
>> So, wiki is properly served via JSON API from the local host.
> That’s a much simpler call.  It doesn’t require any permissions, and it’s a 
> GET call, not a POST call.  That test proves little other than that you have 
> a working JSON API in your local Fossil instance.
> ___
> 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] 'Push done' message

[Richard Hipp]

On 6/7/17, Peter Hardman  wrote:
> The Push done' message from fossil push has an ip: string.
>
> I'm wondering what this means and where it comes from - I'm getting
> 2.0.1.187
> regardless of which server I push to (ppdb.org.uk and chiselapp.com) and
> which
> apparently belongs to a wannadoo.fr server.
>

Are you using a web proxy?

-- 
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] 'Push done' message

[Peter Hardman]

The Push done' message from fossil push has an ip: string.

I'm wondering what this means and where it comes from - I'm getting 2.0.1.187 
regardless of which server I push to (ppdb.org.uk and chiselapp.com) and which 
apparently belongs to a wannadoo.fr server.


Thanks
--

Peter Hardman
___
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] TinyMCE for editing wiki pages

[Paul Hammant]

BSD codebases can use LGPL components/libs without fear of being in
violation of license.

On Wed, Jun 7, 2017 at 6:10 AM, Richard Hipp  wrote:

> On 6/7/17, Chris Rydalch  wrote:
> > I tried following the Cookbook page, but haven't had luck getting it to
> > work. I assume it's because a lot has changed in the last 8 years, both
> > with Fossil and TinyMCE. I tried adapting the instructions, but they
> don't
> > seem to be applicable anymore.
> >
> > Does anyone have a recent example repo using TinyMCE to edit wiki pages?
> >
>
> I had never heard of TinyMCE.  I checked the webpage and it seems nice
> enough.  Unfortunately, the license is LGPL, which I think will make
> it incompatible with the BSD license of Fossil.  Perhaps someone else
> can clarify.
>
> --
> 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] TinyMCE for editing wiki pages

[Richard Hipp]

On 6/7/17, Chris Rydalch  wrote:
> I tried following the Cookbook page, but haven't had luck getting it to
> work. I assume it's because a lot has changed in the last 8 years, both
> with Fossil and TinyMCE. I tried adapting the instructions, but they don't
> seem to be applicable anymore.
>
> Does anyone have a recent example repo using TinyMCE to edit wiki pages?
>

I had never heard of TinyMCE.  I checked the webpage and it seems nice
enough.  Unfortunately, the license is LGPL, which I think will make
it incompatible with the BSD license of Fossil.  Perhaps someone else
can clarify.

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

Re: [fossil-users] Make two fossil repositories "friends" ?

[Richard Hipp]

On 6/6/17, Roy Keene  wrote:
> All,
>
>   I have two Fossil repositories hosted on the same server and
> serving related projects so it would be helpful to me to make them
> "friends" somehow...
>
> Probably as an extension of the login-group functionality (and depndant
> upon it) would be some way to make Fossil look into its friends
> repositories for artifacts that are referenced that are not part of the
> current repository -- it could then just link to the other web interface
> for the other repository (meaning, that part of becoming friends would be
> identifying what the fossil URL prefix is for that peer).
>
> Or something similar.  Right now for example, I have tickets and commits
> that I would like to use the "bracket" notation to refer to tickets and
> commits in other repositories but they are unknown in this repository.
>
> Is such functionality already present in some way that I've missed, or has
> anyone investigated it ?
>

I am not aware of any such functionality nor any such prior investigation.

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

Re: [fossil-users] "fossil http" doubts

[Stephan Beal]

On Wed, Jun 7, 2017 at 8:48 AM, Johan Kuuse  wrote:

> My idea is to make a script which parses the output from all builtin pages.
>

Be aware that fossil makes NO GUARANTEES about the stability of
content/structure of any pages (or CLI command output, for that matter).
Thus any work you do on parsing any pages might be undone by any given
commit to the main fossil tree.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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 http" doubts

[Martin Gagnon]

> Le 7 juin 2017 à 02:48, Johan Kuuse  a écrit :
> 
>> On Tue, Jun 6, 2017 at 6:15 PM, Richard Hipp  wrote:
>>> On 6/6/17, Johan Kuuse  wrote:
>>> Hi,
>>> 
>>> Is there any way to access the Fossil built-in webpages using the "fossil
>>> http"?
>>> In the example below, I try to access the /setup page from localhost,
>>> but it seems I don't get authorized. Instead I get redirected to the
>>> /login page.
>> 
>> You have to log in as a user with "s" (superuser) permission in order
>> to access the /setup page.  If you try to access /setup without the
>> right permissions, you get redirected.
>> 
>> Log in first, then try again.
> 
> Maybe I did not make myself very clear.
> I am running "fossil http" from the command line.
> Is there a way to first "login" from the command line, and then access
> built-in pages such as "/setup", also from the command line?
> 
> My idea is to make a script which parses the output from all builtin pages.
> 

I'm not sure to understand what you want to do but you probably want to use: 
"fossil test-http" instead. 
  https://www.fossil-scm.org/index.html/help?cmd=test-http

-- 
Martin G.___
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 http" doubts

[Johan Kuuse]

On Tue, Jun 6, 2017 at 6:15 PM, Richard Hipp  wrote:
> On 6/6/17, Johan Kuuse  wrote:
>> Hi,
>>
>> Is there any way to access the Fossil built-in webpages using the "fossil
>> http"?
>> In the example below, I try to access the /setup page from localhost,
>> but it seems I don't get authorized. Instead I get redirected to the
>> /login page.
>
> You have to log in as a user with "s" (superuser) permission in order
> to access the /setup page.  If you try to access /setup without the
> right permissions, you get redirected.
>
> Log in first, then try again.

Maybe I did not make myself very clear.
I am running "fossil http" from the command line.
Is there a way to first "login" from the command line, and then access
built-in pages such as "/setup", also from the command line?

My idea is to make a script which parses the output from all builtin pages.

BR,
Johan


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