View Single Post
Old 11-01-2013, 09:18 AM   #29
knc1
\_(ツ)_/ <- Clueless
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 11,140
Karma: 11512569
Join Date: Feb 2012
Location: Central Texas
Device: Nothing KV or newer, not interested.
Quote:
Originally Posted by Aeris View Post
After some pain... here you go:

https://github.com/AerisDev/KindleMenu
Looking good -
Even if just to protect your work from local drive errors.

When using MarkDown for the docs, it is sometimes useful to see how it will render in html before pushing to the repo.

There is a (Lua) script to do just that, which you can find here:
https://bitbucket.org/twobob/kual-sy...DOWN?at=master

I had to hand edit a relatively long 'readme' document from fixed width text to MarkDown for one of my repos -

There where a few differences between the html generated by that script and that generated by the website.
But other than those few 'tweaks' after the first push, the result was very close to what the 'preview' local script generated.
https://bitbucket.org/knc1/kindle-s390-mts

PS: Your Kindle has Lua-5.1 installed, you can use that script on your Kindle.
knc1 is offline   Reply With Quote