9e216da9ef
After go1.16, go will use module mode by default, even when the repository is checked out under GOPATH or in a one-off directory. Add go.mod, go.sum to keep this repo buildable without opting out of the module mode. > go mod init github.com/mmcgrana/gobyexample > go mod tidy > go mod vendor In module mode, the 'vendor' directory is special and its contents will be actively maintained by the go command. pygments aren't the dependency the go will know about, so it will delete the contents from vendor directory. Move it to `third_party` directory now. And, vendor the blackfriday package. Note: the tutorial contents are not affected by the change in go1.16 because all the examples in this tutorial ask users to run the go command with the explicit list of files to be compiled (e.g. `go run hello-world.go` or `go build command-line-arguments.go`). When the source list is provided, the go command does not have to compute the build list and whether it's running in GOPATH mode or module mode becomes irrelevant.
23 lines
873 B
ReStructuredText
23 lines
873 B
ReStructuredText
.. -*- mode: rst -*-
|
|
|
|
================================
|
|
Using Pygments in ReST documents
|
|
================================
|
|
|
|
Many Python people use `ReST`_ for documentation their sourcecode, programs,
|
|
scripts et cetera. This also means that documentation often includes sourcecode
|
|
samples or snippets.
|
|
|
|
You can easily enable Pygments support for your ReST texts using a custom
|
|
directive -- this is also how this documentation displays source code.
|
|
|
|
From Pygments 0.9, the directive is shipped in the distribution as
|
|
`external/rst-directive.py`. You can copy and adapt this code to your liking.
|
|
|
|
.. removed -- too confusing
|
|
*Loosely related note:* The ReST lexer now recognizes ``.. sourcecode::`` and
|
|
``.. code::`` directives and highlights the contents in the specified language
|
|
if the `handlecodeblocks` option is true.
|
|
|
|
.. _ReST: http://docutils.sf.net/rst.html
|