YannL_ has joined #nanoc
koan_ has joined #nanoc
koan has quit [Write error: Connection reset by peer]
YannL has quit [Ping timeout: 257 seconds]
YannL_ is now known as YannL
YannL is now known as Guest43520
ctp has joined #nanoc
ctp_ has joined #nanoc
ctp has quit [Ping timeout: 250 seconds]
VitamineD has quit [Quit: Computer has gone to sleep.]
jonbullock has joined #nanoc
jonbullock has quit [Client Quit]
VitamineD has joined #nanoc
vy has joined #nanoc
<
bobthecow>
that's an erb syntax error.
<
bobthecow>
is chart.js erb?
thomasfuston has joined #nanoc
jugglinmike has joined #nanoc
<
tom[]>
idk: unfortunately not
VitamineD has quit [Ping timeout: 245 seconds]
VitamineD has joined #nanoc
jonbullock has joined #nanoc
jugglinmike has quit [Quit: Leaving.]
<
tom[]>
RuntimeError: The layout file 'layouts/sidenav_doc' is a binary file, but layouts can only be textual
<
guardian>
that's a new check in nanoc 3.7.3
<
tom[]>
how does it help?
<
tom[]>
and what does "textual" mean?
<
tom[]>
the file contains only pritable ascii
<
tom[]>
so a file that has no filename extension can never be a "textual" file
<
tom[]>
how convenient
<
guardian>
layout files are meant to be "textual" in the nanoc.yaml text_extensions sense
<
tom[]>
now i have to rename all my layouts?
<
guardian>
well logic nanoc uses to decide whether things are binary or textual is solely based on file extensions
<
tom[]>
well, again i'm left wondering how this helps
<
guardian>
and generally, people use either .html, .haml, .slim, or .erb I would say
<
guardian>
it helps detecting bugs triggered by people who have binary files in their layouts/ directory, like images
jugglinmike has joined #nanoc
thomasfuston has quit [Read error: Connection reset by peer]
ctp has joined #nanoc
ctp_ has quit [Ping timeout: 245 seconds]
ctp has quit [Ping timeout: 245 seconds]
tom[] has quit [Ping timeout: 240 seconds]
tom[] has joined #nanoc
tom[] has quit [Ping timeout: 255 seconds]
tom[] has joined #nanoc