latest 20 messages by jaybe

+ [2017-07-26T01:05:22Z] jaybe ./flip
+ [2017-07-26T01:05:17Z] jaybe s/blue ox/brown cow/
+ [2017-07-26T01:05:10Z] jaybe the blue ox
+ [2017-07-26T00:38:19Z] jaybe now i must fix the bot regex thing; grrr
+ [2017-07-26T00:38:06Z] jaybe o/
+ [2017-07-26T00:36:21Z] jaybe that will parse out the entire page. variable dimension
+ [2017-07-26T00:36:01Z] jaybe something enlightening if you've not forayed there is to try something simple such as within a post or page: {{ page }}
+ [2017-07-26T00:35:25Z] jaybe when i'm developing a new framework i often use html comments, for example, within different includes and templates... at the top and at the bottom, that specifically identify within the HTML raw source-- what's happening, what's doing what, etc.
+ [2017-07-26T00:34:42Z] jaybe elmiko, there are many different ways to go about providing debugging, tracking, verbosity, etc.
+ [2017-07-26T00:34:12Z] jaybe ;\
+ [2017-07-26T00:34:07Z] jaybe s/"brown cow"/"green cat and open spaces"/
+ [2017-07-26T00:33:52Z] jaybe the brown cow
+ [2017-07-25T23:34:42Z] jaybe ./flip
+ [2017-07-25T23:34:04Z] jaybe there we are \o/
+ [2017-07-25T23:30:44Z] jaybe ./fs trace
+ [2017-07-25T23:30:41Z] jaybe i believe there is also --trace
+ [2017-07-25T23:30:30Z] jaybe elmiko, there is --verbose to begin with
+ [2017-07-25T23:30:16Z] jaybe ./fs debug
+ [2017-07-06T12:35:51Z] jaybe [[ kramdown ]]
+ [2017-07-06T12:35:42Z] jaybe ./fs kramdown