Re: [fossil-users] Minor markdown glitches

2017-07-28 Thread Ross Berteig
On 7/28/2017 11:41 AM, Richard Hipp wrote: On 7/28/17, Florian Balmer wrote: -- * The first list: ... * The second list: `|` `<` ... -- causes a crash Thanks for the bug report. Now fixed on trunk. I *really* wish that Automattic (the owners of

Re: [fossil-users] Minor markdown glitches

2017-07-28 Thread Warren Young
On Jul 28, 2017, at 2:07 PM, Warren Young wrote: > > I didn’t report it because I was able to work around it I just remembered that there was another case I worked around when writing that document: 1. **`n8.c`** **`n8.s`** That should format as two separate

Re: [fossil-users] Minor markdown glitches

2017-07-28 Thread Warren Young
On Jul 28, 2017, at 12:41 PM, Richard Hipp wrote: > > On 7/28/17, Florian Balmer wrote: >> >> -- >> * The first list: ... >> >> * The second list: `|` `<` ... >> -- >> >> causes a crash > > Thanks for the bug report. Now fixed on

Re: [fossil-users] Minor markdown glitches

2017-07-28 Thread Richard Hipp
On 7/28/17, Florian Balmer wrote: > > -- > * The first list: ... > > * The second list: `|` `<` ... > -- > > causes a crash Thanks for the bug report. Now fixed on trunk. -- D. Richard Hipp d...@sqlite.org

[fossil-users] Minor markdown glitches

2017-07-28 Thread Florian Balmer
Maybe not the best idea ☹ but I was taking notes about special characters in batch files on a Fossil markdown/wiki page. It's even worse than what you can imagine, it seems like batch file syntax was designed to stress-test markdown parsers: ! " % & ( ) , ; ^ | < > I enclosed each character