Package chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI- coloured text, etc. Chroma is based heavily on Pygments, and includes translators for Pygments lexers and styles. For more information, go here: https://github.com/alecthomas/chroma
Package bfchroma provides an easy and extensible blackfriday renderer that uses the chroma syntax highlighter to render code blocks.
Package chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI- coloured text, etc. Chroma is based heavily on Pygments, and includes translators for Pygments lexers and styles. For more information, go here: https://github.com/alecthomas/chroma
Package chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI- coloured text, etc. Chroma is based heavily on Pygments, and includes translators for Pygments lexers and styles. For more information, go here: https://github.com/alecthomas/chroma
Package chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI- coloured text, etc. Chroma is based heavily on Pygments, and includes translators for Pygments lexers and styles. For more information, go here: https://github.com/alecthomas/chroma
The present file format Present files have the following format. The first non-blank non-comment line is the title, so the header looks like The subtitle, date, and tags lines are optional. The date line may be written without a time: In this case, the time will be interpreted as 10am UTC on that date. The tags line is a comma-separated list of tags that may be used to categorize the document. The author section may contain a mixture of text, twitter names, and links. For slide presentations, only the plain text lines will be displayed on the first slide. Multiple presenters may be specified, separated by a blank line. After that come slides/sections, each after a blank line: Title of slide or section (must have asterisk) Some Text ** Subsection bullets more bullets a bullet with *** Sub-subsection Some More text Preformatted text is indented (however you like) Further Text, including invocations like: .code x.go /^func main/,/^}/ .play y.go .image image.jpg .background image.jpg .iframe http://foo .link http://foo label .html file.html .caption _Gopher_ by [[https://www.instagram.com/reneefrench/][Renée French]] Again, more text Blank lines are OK (not mandatory) after the title and after the text. Text, bullets, and .code etc. are all optional; title is not. Lines starting with # in column 1 are commentary. Fonts: Within the input for plain text or lists, text bracketed by font markers will be presented in italic, bold, or program font. Marker characters are _ (italic), * (bold) and ` (program font). An opening marker must be preceded by a space or punctuation character or else be at start of a line; similarly, a closing marker must be followed by a space or punctuation character or else be at the end of a line. Unmatched markers appear as plain text. There must be no spaces between markers. Within marked text, a single marker character becomes a space and a doubled single marker quotes the marker character. Inline links: Links can be included in any text with the form [url[label]], or [url] to use the URL itself as the label. Functions: A number of template functions are available through invocations in the input text. Each such invocation contains a period as the first character on the line, followed immediately by the name of the function, followed by any arguments. A typical invocation might be (except that the ".play" must be at the beginning of the line and not be indented like this.) Here follows a description of the functions: code: Injects program source into the output by extracting code from files and injecting them as HTML-escaped <pre> blocks. The argument is a file name followed by an optional address that specifies what section of the file to display. The address syntax is similar in its simplest form to that of ed, but comes from sam and is more general. See for full details. The displayed block is always rounded out to a full line at both ends. If no pattern is present, the entire file is displayed. Any line in the program that ends with the four characters is deleted from the source before inclusion, making it easy to write things like to find snippets like this and see only this: Also, inside the displayed text a line that ends will be highlighted in the display. A highlighting mark may have a suffix word, such as Such highlights are enabled only if the code invocation ends with "HL" followed by the word: The .code function may take one or more flags immediately preceding the filename. This command shows test.go in an editable text area: This command shows test.go with line numbers: play: The function "play" is the same as "code" but puts a button on the displayed source so the program can be run from the browser. Although only the selected text is shown, all the source is included in the HTML output so it can be presented to the compiler. link: Create a hyperlink. The syntax is 1 or 2 space-separated arguments. The first argument is always the HTTP URL. If there is a second argument, it is the text label to display for this link. image: The template uses the function "image" to inject picture files. The syntax is simple: 1 or 3 space-separated arguments. The first argument is always the file name. If there are more arguments, they are the height and width; both must be present, or substituted with an underscore. Replacing a dimension argument with the underscore parameter preserves the aspect ratio of the image when scaling. video: The template uses the function "video" to inject video files. The syntax is simple: 2 or 4 space-separated arguments. The first argument is always the file name. The second argument is always the file content-type. If there are more arguments, they are the height and width; both must be present, or substituted with an underscore. Replacing a dimension argument with the underscore parameter preserves the aspect ratio of the video when scaling. background: The template uses the function "background" to set the background image for a slide. The only argument is the file name of the image. caption: The template uses the function "caption" to inject figure captions. The text after ".caption" is embedded in a figcaption element after processing styling and links as in standard text lines. iframe: The function "iframe" injects iframes (pages inside pages). Its syntax is the same as that of image. html: The function html includes the contents of the specified file as unescaped HTML. This is useful for including custom HTML elements that cannot be created using only the slide format. It is your responsibility to make sure the included HTML is valid and safe. Presenter notes: Presenter notes may be enabled by appending the "-notes" flag when you run your "present" binary. This will allow you to open a second window by pressing 'N' from your browser displaying your slides. The second window is completely synced with your main window, except that presenter notes are only visible on the second window. Lines that begin with ": " are treated as presenter notes. Title of slide Some Text : Presenter notes (first paragraph) : Presenter notes (subsequent paragraph(s)) Notes may appear anywhere within the slide text. For example: Title of slide : Presenter notes (first paragraph) Some Text : Presenter notes (subsequent paragraph(s)) This has the same result as the example above.
Package gi is the top-level repository for the GoGi GUI framework. All of the code is in the sub-packages within this repository: * gist: css-based styling settings, including Color * girl: rendering library, can be used standalone, SVG compliant * gi: the main 2D GUI Node, Widgets, and Window * giv: more complex Views of Go data structures, supporting Model-View paradigm. * svg: full SVG rendering framework, used for Icons in gi. * gi3d: 3D rendering of a Scene within 2D windows -- full interactive 3D scenegraph. * histyle: text syntax-based highlighting styles -- used in giv.TextView * python: access all of GoGi from within Python using GoPy system.
Package chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI- coloured text, etc. Chroma is based heavily on Pygments, and includes translators for Pygments lexers and styles. For more information, go here: https://github.com/alecthomas/chroma
Package chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI- coloured text, etc. Chroma is based heavily on Pygments, and includes translators for Pygments lexers and styles. For more information, go here: https://github.com/alecthomas/chroma
Package chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI- coloured text, etc. Chroma is based heavily on Pygments, and includes translators for Pygments lexers and styles. For more information, go here: https://github.com/alecthomas/chroma
Package chroma takes source code and other structured text and converts it into syntax highlighted HTML, ANSI- coloured text, etc. Chroma is based heavily on Pygments, and includes translators for Pygments lexers and styles. For more information, go here: https://github.com/alecthomas/chroma
Package syntax provides syntax highlighting for code. It currently uses a language-independent lexer and performs decently on JavaScript, Java, Ruby, Python, Go, and C.
Vox is a Go package designed to help make terminal/console applications more attractive. It is a collection of small helper functions that aid in printing various pieces of information to the console. - Various predefined and common printing tasks like printing property key/value pairs, result responses, etc. - Print JSON data with syntax highlighting - Easily print colorized output - Display real time progress bars for tasks - Easy helper functions for printing various types of messages: Alerts, errors, debug messages, etc. - Control the output and input streams to help during application testing. There are a number of output functions to print data to the screen with out without coloring. Most of the output functions accept an a series of string parts that are combined together. Color constants can be interlaced between these parts to color the output. There are also a number of "LogLevel" type functions that easily color the output. There are several helper functions for gathering input from the console. Vox offers pipelines as a way of configuring one or more output streams. Four built in pipelines are provided with the package: - ConsolePipeline - This is the default Pipeline set for any vox instance. This pipeline will present colored output to standard out. - FilePipeline - This pipeline will redirect all data to a local file. This pipeline uses plain output, without color codes. - TestPipeline - All output will be internally stored in a string slice and utility functions are provided to make accessing values easier. This pipeline should be used for unit tests. - WriterPipeline - This is a generic pipeline that allows you to specifiy any writer that implements the io.Writer interface. A testing pipeline is provided that directs all output into an internal string slice. It also provides utility functions to make accessing values easier. A Test helper function is provided to make this easier: You can use the `SendInput` function. SendInput must be called before any prompt function, so that the data is ready in the buffer when `Prompt` is called.