00:00:00 --- log: started retro/17.07.19 01:04:14 --- join: ratanasov (4e82943e@gateway/web/freenode/ip.78.130.148.62) joined #retro 04:44:14 most of the names are based on maori word names, with some minor changes to spelling 04:44:46 and the four backticks was what I had encountered initially. If three is more common, I'll adapt the code to support this. 04:46:41 I think 3 is used almost universally (among the flavors that support fenced code at all)... 04:47:53 But I checked - the CommonMark spec says 3 or more... http://spec.commonmark.org/0.12/#fenced-code-blocks 04:49:49 Another thing I noticed is that file:read returns 0 on EOF, which might prevent us from reading binary files containing zeros... 04:50:36 C's EOF is a negative value, I think and we might use -1 or something else for file:read... 04:52:03 Positive values outside of the ASCII range might become handy in case we add some encoding support in the future and let file:getc read UTF-8 encoded characters. 04:58:45 --- quit: ratanasov (Ping timeout: 260 seconds) 04:59:09 --- join: ratanasov (4e82943e@gateway/web/freenode/ip.78.130.148.62) joined #retro 05:33:14 for binary files, I have always just checked the current pointer against the file size 05:55:19 would it make sense to also support the ~~~ delimiter for fenced code? 05:59:54 I didn't know about it until today... :) 06:06:57 ok, support for both is in the repo now 06:08:55 Great, thanks. 06:09:04 --- quit: ratanasov (Quit: Page closed) 08:15:49 --- join: ratanasov (~ratanasov@89.25.76.2) joined #retro 08:41:26 --- quit: ratanasov (Quit: Leaving) 09:29:04 --- join: FreeFull (~freefull@defocus/sausage-lover) joined #retro 23:01:38 --- quit: FreeFull () 23:59:59 --- log: ended retro/17.07.19