Re: [fossil-users] Fossil can not import its own git export

2017-03-14 Thread Martin Gagnon
On Tue, Mar 14, 2017 at 08:48:50PM -0500, Artur Shepilko wrote: > Just tried the case of "file name contains a newline char" with git. > Looks like git encodes such names with C-like characters ('\n' for x0A > or '\r' for x0D). > > Git fast-export outputs such files enquoted as follows: > M

Re: [fossil-users] Fossil can not import its own git export

2017-03-14 Thread Artur Shepilko
Just tried the case of "file name contains a newline char" with git. Looks like git encodes such names with C-like characters ('\n' for x0A or '\r' for x0D). Git fast-export outputs such files enquoted as follows: M 100644 :1 "newline\nfile.txt" For the same case, fossil export does not encode

Re: [fossil-users] Old fossil (1.29) accessing current fossil trunk?

2017-03-14 Thread Stephan Beal
On Wed, Mar 15, 2017 at 1:25 AM, Stephan Beal wrote: > Yes, it can accept JSON input (even from the CLI). For the full details > see: > > https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2q > NUkBEgiUvoqFN4/view > > and: > > fossil help json > > doh - it

Re: [fossil-users] Old fossil (1.29) accessing current fossil trunk?

2017-03-14 Thread Stephan Beal
On Tue, Mar 14, 2017 at 11:06 PM, Stefan Bellon wrote: > On Mon, 13 Mar, Ross Berteig wrote: > > > When fossil is configured to include JSON support it has a fossil > > json command that consumes a JSON object full of command and > > arguments and returns a JSON object of

Re: [fossil-users] Old fossil (1.29) accessing current fossil trunk?

2017-03-14 Thread Ross Berteig
On 3/14/2017 3:06 PM, Stefan Bellon wrote: On Mon, 13 Mar, Ross Berteig wrote: When fossil is configured to include JSON support it has a fossil json command that consumes a JSON object full of command and arguments and returns a JSON object of results. A similar feature is available over

Re: [fossil-users] Old fossil (1.29) accessing current fossil trunk?

2017-03-14 Thread Stefan Bellon
On Mon, 13 Mar, Ross Berteig wrote: > When fossil is configured to include JSON support it has a fossil > json command that consumes a JSON object full of command and > arguments and returns a JSON object of results. A similar feature is > available over HTTP(S) through URLs beginning with /json.

Re: [fossil-users] Old fossil (1.29) accessing current fossil trunk?

2017-03-14 Thread Stefan Bellon
On Mon, 13 Mar, Richard Hipp wrote: > I'm a little confused. If you need to continue using Fossil 1.29 for > text output compatibility, then why is it a problem that you cannot > "fossil update" to the latest trunk? After all, you won't be using > the latest trunk, right? Ha, right, that's a

Re: [fossil-users] Support for commonmark markdown in fossil

2017-03-14 Thread Jan Nijtmans
2017-03-14 16:27 GMT+01:00 Mark Janssen: > Or in patch form: ... http://fossil-scm.org/index.html/info/dd41f85acf57290a Thanks! Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Support for commonmark markdown in fossil

2017-03-14 Thread Mark Janssen
Or in patch form: @@ -460,15 +460,16 @@ while( i=size ) return 0; -if( data[i]==c ) return i; /* not counting escaped chars */ if( i && data[i-1]=='\\' ){ i++; continue; } + +if( data[i]==c ) return i; /* skipping a code span */ if(

Re: [fossil-users] Support for commonmark markdown in fossil

2017-03-14 Thread Natacha Porté
Hello, on Tuesday 14 March 2017 at 15:44, Mark Janssen wrote: > I did notice a (IMO) bug during the conversion: > > $ cat markdown-test2.md > _test\_embedded_ > *test\*embedded* > $ fossil test-markdown-render markdown-test2.md > > > testembedded_ > testembedded* > > > > The escaped

Re: [fossil-users] Support for commonmark markdown in fossil

2017-03-14 Thread Mark Janssen
On Sat, Mar 11, 2017 at 6:18 PM, Natacha Porté wrote: > > > I should really clarify that it was about *fenced* code blocks, since > traditional markdown code blocks are correctly supported (unless there > is a serious bug in there). > > I do understand the use of code