~duangle/scopes-patch

[patch] conversion to markdown (mkdocs) format documentation

Details
Message ID
<CAAhSavZcdU6GFbCBvtGw3BtX_tFAJXuM-bJtzm7qg4JTHRGhSw@mail.gmail.com>
DKIM signature
missing
Download raw message
Greetings,

I've finally finished converting Scopes' documentation to markdown
(mkdocs) format.  I managed to get syntax highlighting working using
the existing scopeslexer after updating it (trivially) to Python 3.

Because of the size of the changes, I've chosen to instead supply the
"patches" via a fork of the Scopes repo on hg.sr.ht:

https://hg.sr.ht/~binarycrusader/scopes-md/log

You will want these changesets in this order:

https://hg.sr.ht/~binarycrusader/scopes-md/rev/066781654776397011580f4eae9035dbb66cb8fc
https://hg.sr.ht/~binarycrusader/scopes-md/rev/80bcde20373036b13b423c43e5f61516a1800684
https://hg.sr.ht/~binarycrusader/scopes-md/rev/5388b093e2c49b5f5bac1cbd7fdec77553b5cd70
https://hg.sr.ht/~binarycrusader/scopes-md/rev/6f7c6a0a71345e3b49fdb372531df2a61bb5818b
https://hg.sr.ht/~binarycrusader/scopes-md/rev/7e29aedecda1b1bac0f5d4f341db694af8b0e949

You should be able to create a local clone of the repository and then
use "hg graft" or "hg transplant" to cherry-pick the changes from my
fork to another hg repo.

markdown is not nearly as well-suited to formal documentation writing
as restructured text, but it's what all the cool people use these days
I guess...

Feedback welcome.

-- 
Shawn Walker-Salas
Reply to thread Export thread (mbox)