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,
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
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
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
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:
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
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
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
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
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
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
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 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
>
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
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
> >
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
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
>
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
> 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
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
20 matches
Mail list logo