[elpa] externals/beardbolt 9b2c85397c 149/323: Add texinfo version of docs

[ELPA Syncer]

branch: externals/beardbolt
commit 9b2c85397cf8e9a173c0ddf4132f4932b0723219
Author: Jay Kamat <jaygkamat@gmail.com>
Commit: Jay Kamat <jaygkamat@gmail.com>

    Add texinfo version of docs
---
 README.org       | 103 ++----------------
 doc/.gitignore   |   1 +
 doc/gen.sh       |   2 +
 doc/rmsbolt.org  | 202 ++++++++++++++++++++++++++++++++++
 doc/rmsbolt.texi | 324 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 5 files changed, 539 insertions(+), 93 deletions(-)

diff --git a/README.org b/README.org
index c6d75b1bd4..9fbdcb2417 100644
--- a/README.org
+++ b/README.org
@@ -1,12 +1,18 @@
+
 * [[https://gitlab.com/jgkamat/rmsbolt][RMSbolt]] 
[[https://melpa.org/#/rmsbolt][file:https://melpa.org/packages/rmsbolt-badge.svg]]
 
 A supercharged implementation of the 
[[https://github.com/mattgodbolt/compiler-explorer][godbolt compiler-explorer]] 
for Emacs.
 
-RMSBolt tries to make it easy to see what your compiler is doing. It does this
+RMSbolt tries to make it easy to see what your compiler is doing. It does this
 by showing you the assembly output of a given source code file. It also
 highlights which source code a given assembly block corresponds to, and vice
 versa. It supports more types of languages than any previous tool of its kind.
 
+* [[file:doc/rmsbolt.org][Documentation]]
+
+This README is a condensed version of the docs. [[file:doc/rmsbolt.org][For 
full usage instructions,
+please start at the docs (also available through info).]]
+
 * Why RMSbolt over godbolt?
 
 - Much more flexible and powerful:
@@ -62,11 +68,11 @@ enable ~rmsbolt-mode~ in a supported language. Then run 
~rmsbolt-compile~ or
 use the default ~C-c C-c~ binding. After the first run, the buffer should
 automatically update.
 
-Language-specific quirks are listed in the demos section currently.
+Language-specific quirks are listed in the full documentation.
 
 * Configuration
 
-RMSBolt is primarily configured with Emacs local variables. This lets you 
change
+RMSbolt is primarily configured with Emacs local variables. This lets you 
change
 compiler and rmsbolt options simply by editing a local variable block. The
 starter files have this block with some common settings:
 
@@ -80,119 +86,30 @@ starter files have this block with some common settings:
 *Note*: 
[[https://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html#Specifying-File-Variables][the
 Local Variable block must be 3000 characters from the end of the
 file to work]]. Any method of setting buffer-local variables will work though.
 
-Notable options:
-
-| Option                        | Description                                  
                                                                                
 |
-|-------------------------------+-------------------------------------------------------------------------------------------------------------------------------|
-| ~rmsbolt-command~             | determines the prefix of the compilation 
command to use. Use this to switch between compilers or pass flags to your 
compiler. |
-| ~rmsbolt-default-directory~   | determines the default-drectory to compile 
from.                                                                           
   |
-| ~rmsbolt-disassemble~         | disassemble from a compiled binary with 
objdump, if supported.                                                          
      |
-| ~rmsbolt-filter-*~            | Tweak filtering of binary output             
                                                                                
 |
-| ~rmsbolt-asm-format~          | Switch between different output formats. 
Most binary formats support "att" and "intel"                                   
     |
-| ~rmsbolt-demangle~            | Demangle the output, if supported.           
                                                                                
 |
-| ~rmsbolt-ignore-binary-limit~ | Ignore the binary size limit for 
disassembly. This will almost certainly cause Emacs to hang during large 
processing.         |
+The main knobs are described in the full documentation.
 
 * Demos
 ** C/C++
-
 [[https://i.imgur.com/Rox6y0U.gif][https://i.imgur.com/Rox6y0U.gif]]
-
-
 ** OCaml
-
 [[https://i.imgur.com/369Ylxk.gif][https://i.imgur.com/369Ylxk.gif]]
-
 ** Rust
-
-demangling is done with rustfilt if available
-
 [[https://i.imgur.com/nW1lVFM.gif][https://i.imgur.com/nW1lVFM.gif]]
-
 ** Haskell
-
-demangling is done with the compiler-explorer demangler, named
-to ~haskell-demangler~.
-
 [[https://i.imgur.com/fAQQMJe.gif][https://i.imgur.com/fAQQMJe.gif]]
-
 ** Python
-
-Support for viewing bytecode only. Python 
[[https://bugs.python.org/issue2506][doesn't have many options]], so most
-tweakables will not work. Python 3.7 is required for recursion into functions,
-otherwise only top level code will be shown. Python 2 is unsupported.
-
 [[https://i.imgur.com/cMYfkGx.gif][https://i.imgur.com/cMYfkGx.gif]]
-
 ** Java
-
-Parses the output of ~javap~, so may be a little unreliable or buggy at the
-moment.
-
 [[https://i.imgur.com/KkWEMMj.gif][https://i.imgur.com/KkWEMMj.gif]]
-
 ** PHP
-Requires the [[https://github.com/derickr/vld][vld php extension]] to display 
PHP opcodes.
-
-If you use hack, you will not get source->asm matching or filtering.
-
 [[https://i.imgur.com/xBfzaK9.gif][https://i.imgur.com/xBfzaK9.gif]]
 ** Pony
-
-Filtering on pony is not as effective as pony asm includes references to
-machine-generated functions. This means the output will be slower to generate,
-similar to disassembly in other languages. The pony file being viewed will be
-copied into it's own directory, making it much harder to view non-toy examples.
-
 [[https://i.imgur.com/8kd6kkJ.gif][https://i.imgur.com/8kd6kkJ.gif]]
-
 ** Emacs Lisp
-
-No support for source->asm matching, filtering, or automatic recompile.
-
-Emacs 26 or the ~cl-print~ package are required.
-
 [[https://i.imgur.com/uYrQ7En.gif][https://i.imgur.com/uYrQ7En.gif]]
-
 ** Common Lisp
-
-No support for source->asm matching or filtering. Only ~sbcl~ and ~clisp~
-supported at the moment, with ~sbcl~ giving much better results.
-
 [[https://i.imgur.com/36aNVvf.gif][https://i.imgur.com/36aNVvf.gif]]
 
-* Adding a Language
-
-Adding support for a new language is fairly easy. The closer it is to existing
-compilers, the easier it will be (to the point where a clone of a C compiler is
-just a couple copy-paste lines). However, it is not excessively hard to add
-support for completely foreign compilers and bytecode/assembly formats.
-
-As a minimum starting point, you must know how to compile a source file to
-assembly or bytecode on the command line, and know how the line numbers are
-available in the compiled form if they exist.
-
-1. [[file:rmsbolt.el::;;;;%20Language%20Definitions][Add a new entry to the 
language definitions statement.]]
-   - To do this, you will need to (at a minimum) add a mode, compile-command, a
-     compile-cmd-function, and a starter file name.
-   - The compile-cmd-function is a function that will turn local variable
-     settings into a valid command which will take in a filename and output
-     assembly or an executable. See ~rmsbolt--c-compile-cmd~ for an example.
-   - When building compilation commands, please make sure to use absolute 
paths,
-     as the default-directory is not guaranteed to be stable.
-   - If the assembly is not in a standard format, you will need to define a
-     ~process-asm-custom-fn~ as well (see python/java for examples).
-   - If you would like to add language tweaks in your own config (ie: take full
-     control over what rmsbolt does completely), you can use
-     ~rmsbolt-language-descriptor~ to fully override the defaults with a custom
-     language definition.
-2. [[file:rmsbolt.el::;;;;;%20Starter%20Definitions][Add a new entry into the 
starter file]]
-   - For this, you will need to make a starter file. See 
[[file:starters/][this folder]] for
-     existing examples.
-   - Ideally, try to pick something which is interesting to play with from an
-     disassembly point of view.
-
-You're done!
-
 * Community and Support
 
 There isn't a dedicated place to discuss this yet, but I (~jgkamat~) hang out 
in
diff --git a/doc/.gitignore b/doc/.gitignore
new file mode 100644
index 0000000000..eb401dc42d
--- /dev/null
+++ b/doc/.gitignore
@@ -0,0 +1 @@
+rmsbolt.texi~
diff --git a/doc/gen.sh b/doc/gen.sh
new file mode 100755
index 0000000000..53261b50cc
--- /dev/null
+++ b/doc/gen.sh
@@ -0,0 +1,2 @@
+#!/bin/sh
+emacs rmsbolt.org --batch -l ox-texinfo -f org-texinfo-export-to-texinfo
diff --git a/doc/rmsbolt.org b/doc/rmsbolt.org
new file mode 100644
index 0000000000..32a90c87d1
--- /dev/null
+++ b/doc/rmsbolt.org
@@ -0,0 +1,202 @@
+#+TITLE: RMSbolt User Manual
+:PREAMBLE:
+#+AUTHOR: Jay Kamat
+#+EMAIL: jaygkamat@gmail.com
+#+DATE: <2018-10-27 Sat>
+#+LANGUAGE: en
+
+#+TEXINFO_DIR_CATEGORY: Emacs
+#+TEXINFO_DIR_TITLE: RMSbolt: (rmsbolt).
+#+TEXINFO_DIR_DESC: Viewing disassembly in Emacs with RMSbolt.
+#+BIND: ox-texinfo+-before-export-hook ox-texinfo+-update-version-strings
+
+#+OPTIONS: H:4 num:3 toc:2
+
+RMSbolt is a compiler output viewer in Emacs.
+
+RMSbolt tries to make it easy to see what your compiler is doing. It does this
+by showing you the assembly output of a given source code file. It also
+highlights which source code a given assembly block corresponds to, and vice
+versa. It supports more types of languages than any previous tool of its kind.
+
+* Installation
+A [[https://melpa.org/#/rmsbolt][melpa package]] is available for rmsbolt.
+
+No dependencies are required, other than an Emacs newer than 25.1
+
+** Quelpa
+
+This is a quelpa formula for RMSbolt
+
+#+BEGIN_SRC emacs-lisp
+  (quelpa '(rmsbolt
+            :files (:defaults "starters")
+            :fetcher gitlab
+            :repo "jgkamat/rmsbolt"))
+#+END_SRC
+
+* Running
+Once installed, use the ~rmsbolt-starter~ command to generate starter files, or
+enable ~rmsbolt-mode~ in a supported language. Then run ~rmsbolt-compile~ or 
use
+the default ~C-c C-c~ binding to pop open a disassembly buffer. After the first
+run, the buffer should automatically update.
+* Configuring
+
+RMSbolt is primarily configured with Emacs local variables. This lets you 
change
+compiler and rmsbolt options simply by editing a local variable block. The
+starter files have this block with some common settings:
+
+#+BEGIN_SRC c
+  // Local Variables:
+  // rmsbolt-command: "gcc -O0"
+  // rmsbolt-disassemble: nil
+  // End:
+#+END_SRC
+
+*Note*: 
[[https://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html#Specifying-File-Variables][the
 Local Variable block must be 3000 characters from the end of the
+file to work]]. Any method of setting buffer-local variables will work though.
+
+** Option List
+
+- Local Option: rmsbolt-command
+
+  Determines the prefix of the compilation command to use. Use this to switch
+  between compilers or pass flags to your compiler.
+
+- Local Option: rmsbolt-default-directory
+
+  Determines the default directory to compile from, which is useful if you are
+  building with a build-system.
+
+- Local Option: rmsbolt-disassemble
+
+  Disassemble from a compiled binary with objdump, if supported.
+
+- Local Option: rmsbolt-filter-directives
+
+  Whether to filter unused assembly directives out of final output.
+
+- Local Option: rmsbolt-filter-labels
+
+  Whether to filter unused labels from final output
+
+- Local Option: rmsbolt-filter-comment-only
+
+  Whether to filter lines that are comment-only.
+
+- Local Option: rmsbolt-asm-format
+
+  Which output format to use. Supported values vary between languages. In
+  general, ~"intel"~ and ~"att"~ are supported. ~nil~ means to use the tool's
+  defaults. Other values may work as well, depending on your compiler.
+
+- Local Option: rmsbolt-demangle
+
+  Demangle the output, if supported.
+
+- Local Option: rmsbolt-ignore-binary-limit
+
+  Ignore the binary size limit for disassembly. This will almost certainly 
cause
+  Emacs to hang during large processing.
+
+- Local Option: rmsbolt-demangle
+
+  Enable or disable demangling, if the language supports it.
+
+* Languages
+This section covers languages-specific quirks and features.
+
+** C/C++
+
+C/C++ is the primary focus of support, and will get new features and support
+first.
+
+Demangling is enabled if ~c++filt~ is available on the path.
+
+** OCaml
+
+OCaml disassembly is supported through both ~ocamlopt~ and through disassembly
+with objdump.
+
+** Rust
+
+Demangling is done with ~rustfilt~ if it is on the path.
+
+** Haskell
+
+Demangling is done with the compiler-explorer demangler, named
+to ~haskell-demangler~ and placed on the path.
+
+
+** Python
+
+Support for viewing bytecode only. Python 
[[https://bugs.python.org/issue2506][doesn't have many options]], so most
+tweakables will not work. Python 3.7 is required for recursion into functions,
+otherwise only top level code will be shown. Python 2 is completely 
unsupported.
+
+** Java
+
+Parses the output of ~javap~ to get debug information and disassembly.
+
+
+** PHP
+Requires the [[https://github.com/derickr/vld][vld php extension]] to display 
PHP opcodes. Without that, you will
+not get any output.
+
+If you use hack (denoted by ~<hh?~ at the top of your file), you will not get
+source->asm matching or filtering.
+
+** Pony
+
+Filtering on pony is not as effective as pony asm includes references to
+machine-generated functions. This means the output will be slower to generate,
+similar to disassembly in other languages. The pony file being viewed will be
+copied into it's own directory, making it much harder to view non-toy examples.
+
+** Emacs Lisp
+
+No support for source->asm matching, filtering, or automatic recompile.
+
+Emacs 26 or the ~cl-print~ package are required.
+
+** Common Lisp
+
+No support for source->asm matching or filtering. Only ~sbcl~ and ~clisp~
+supported at the moment, with ~sbcl~ giving much better results.
+
+* Developing
+
+These are some tips which will help people working on developing or 
customizing RMSbolt.
+
+** Adding a Language
+
+Adding support for a new language is fairly easy. The closer it is to existing
+compilers, the easier it will be (to the point where a clone of a C compiler is
+just a couple copy-paste lines). However, it is not excessively hard to add
+support for completely foreign compilers and bytecode/assembly formats.
+
+As a minimum starting point, you must know how to compile a source file to
+assembly or bytecode on the command line, and know how the line numbers are
+available in the compiled form if they exist.
+
+1. [[file:../rmsbolt.el::;;;;%20Language%20Definitions][Add a new entry to the 
language definitions statement.]]
+   - To do this, you will need to (at a minimum) add a mode, compile-command, a
+     compile-cmd-function, and a starter file name.
+   - The compile-cmd-function is a function that will turn local variable
+     settings into a valid command which will take in a filename and output
+     assembly or an executable. See ~rmsbolt--c-compile-cmd~ for an example.
+   - When building compilation commands, please make sure to use absolute 
paths,
+     as the default-directory is not guaranteed to be stable.
+   - If the assembly is not in a standard format, you will need to define a
+     ~process-asm-custom-fn~ as well (see python/java for examples).
+   - If you would like to add language tweaks in your own config (ie: take full
+     control over what rmsbolt does completely), you can use
+     ~rmsbolt-language-descriptor~ to fully override the defaults with a custom
+     language definition.
+2. [[file:../rmsbolt.el::;;;;;%20Starter%20Definitions][Add a new entry into 
the starter file]]
+   - For this, you will need to make a starter file. See 
[[file:./../starters/][this folder]] for
+     existing examples.
+   - Ideally, try to pick something which is interesting to play with from an
+     disassembly point of view.
+
+You're done!
diff --git a/doc/rmsbolt.texi b/doc/rmsbolt.texi
new file mode 100644
index 0000000000..fd55b40cf3
--- /dev/null
+++ b/doc/rmsbolt.texi
@@ -0,0 +1,324 @@
+\input texinfo    @c -*- texinfo -*-
+@c %**start of header
+@setfilename ./rmsbolt.info
+@settitle RMSbolt User Manual
+@documentencoding UTF-8
+@documentlanguage en
+@c %**end of header
+
+@dircategory Emacs
+@direntry
+* RMSbolt: (rmsbolt).   Viewing disassembly in Emacs with RMSbolt.
+@end direntry
+
+@finalout
+@titlepage
+@title RMSbolt User Manual
+@author Jay Kamat
+@end titlepage
+
+@contents
+
+@ifnottex
+@node Top
+@top RMSbolt User Manual
+@end ifnottex
+
+@menu
+* Installation::
+* Running::
+* Configuring::
+* Languages::
+* Developing::
+
+@detailmenu
+--- The Detailed Node Listing ---
+
+Installation
+
+* Quelpa::
+
+Configuring
+
+* Option List::
+
+Languages
+
+* C/C++::
+* OCaml::
+* Rust::
+* Haskell::
+* Python::
+* Java::
+* PHP::
+* Pony::
+* Emacs Lisp::
+* Common Lisp::
+
+Developing
+
+* Adding a Language::
+@end detailmenu
+@end menu
+
+:PREAMBLE:
+RMSbolt is a compiler output viewer in Emacs.
+
+RMSbolt tries to make it easy to see what your compiler is doing. It does this
+by showing you the assembly output of a given source code file. It also
+highlights which source code a given assembly block corresponds to, and vice
+versa. It supports more types of languages than any previous tool of its kind.
+
+@node Installation
+@chapter Installation
+
+A @uref{https://melpa.org/#/rmsbolt,melpa package} is available for rmsbolt.
+
+No dependencies are required, other than an Emacs newer than 25.1
+@menu
+* Quelpa::
+@end menu
+
+@node Quelpa
+@section Quelpa
+
+This is a quelpa formula for RMSbolt
+
+@lisp
+(quelpa '(rmsbolt
+         :files (:defaults "starters")
+         :fetcher gitlab
+         :repo "jgkamat/rmsbolt"))
+@end lisp
+
+@node Running
+@chapter Running
+
+Once installed, use the @code{rmsbolt-starter} command to generate starter 
files, or
+enable @code{rmsbolt-mode} in a supported language. Then run 
@code{rmsbolt-compile} or use
+the default @code{C-c C-c} binding to pop open a disassembly buffer. After the 
first
+run, the buffer should automatically update.
+
+@node Configuring
+@chapter Configuring
+
+RMSbolt is primarily configured with Emacs local variables. This lets you 
change
+compiler and rmsbolt options simply by editing a local variable block. The
+starter files have this block with some common settings:
+
+@example
+// Local Variables:
+// rmsbolt-command: "gcc -O0"
+// rmsbolt-disassemble: nil
+// End:
+@end example
+
+@strong{Note}: 
@uref{https://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html#Specifying-File-Variables,the
 Local Variable block must be 3000 characters from the end of the
+file to work}. Any method of setting buffer-local variables will work though.
+@menu
+* Option List::
+@end menu
+
+@node Option List
+@section Option List
+
+@itemize
+@item
+Local Option: rmsbolt-command
+
+Determines the prefix of the compilation command to use. Use this to switch
+between compilers or pass flags to your compiler.
+
+@item
+Local Option: rmsbolt-default-directory
+
+Determines the default directory to compile from, which is useful if you are
+building with a build-system.
+
+@item
+Local Option: rmsbolt-disassemble
+
+Disassemble from a compiled binary with objdump, if supported.
+
+@item
+Local Option: rmsbolt-filter-directives
+
+Whether to filter unused assembly directives out of final output.
+
+@item
+Local Option: rmsbolt-filter-labels
+
+Whether to filter unused labels from final output
+
+@item
+Local Option: rmsbolt-filter-comment-only
+
+Whether to filter lines that are comment-only.
+
+@item
+Local Option: rmsbolt-asm-format
+
+Which output format to use. Supported values vary between languages. In
+general, ~"intel"~ and ~"att"~ are supported. @code{nil} means to use the 
tool's
+defaults. Other values may work as well, depending on your compiler.
+
+@item
+Local Option: rmsbolt-demangle
+
+Demangle the output, if supported.
+
+@item
+Local Option: rmsbolt-ignore-binary-limit
+
+Ignore the binary size limit for disassembly. This will almost certainly cause
+Emacs to hang during large processing.
+
+@item
+Local Option: rmsbolt-demangle
+
+Enable or disable demangling, if the language supports it.
+@end itemize
+
+@node Languages
+@chapter Languages
+
+This section covers languages-specific quirks and features.
+@menu
+* C/C++::
+* OCaml::
+* Rust::
+* Haskell::
+* Python::
+* Java::
+* PHP::
+* Pony::
+* Emacs Lisp::
+* Common Lisp::
+@end menu
+
+@node C/C++
+@section C/C++
+
+C/C++ is the primary focus of support, and will get new features and support
+first.
+
+Demangling is enabled if @code{c++filt} is available on the path.
+
+@node OCaml
+@section OCaml
+
+OCaml disassembly is supported through both @code{ocamlopt} and through 
disassembly
+with objdump.
+
+@node Rust
+@section Rust
+
+Demangling is done with @code{rustfilt} if it is on the path.
+
+@node Haskell
+@section Haskell
+
+Demangling is done with the compiler-explorer demangler, named
+to @code{haskell-demangler} and placed on the path.
+
+@node Python
+@section Python
+
+Support for viewing bytecode only. Python 
@uref{https://bugs.python.org/issue2506,doesn't have many options}, so most
+tweakables will not work. Python 3.7 is required for recursion into functions,
+otherwise only top level code will be shown. Python 2 is completely 
unsupported.
+
+@node Java
+@section Java
+
+Parses the output of @code{javap} to get debug information and disassembly.
+
+@node PHP
+@section PHP
+
+Requires the @uref{https://github.com/derickr/vld,vld php extension} to 
display PHP opcodes. Without that, you will
+not get any output.
+
+If you use hack (denoted by @code{<hh?} at the top of your file), you will not 
get
+source->asm matching or filtering.
+
+@node Pony
+@section Pony
+
+Filtering on pony is not as effective as pony asm includes references to
+machine-generated functions. This means the output will be slower to generate,
+similar to disassembly in other languages. The pony file being viewed will be
+copied into it's own directory, making it much harder to view non-toy examples.
+
+@node Emacs Lisp
+@section Emacs Lisp
+
+No support for source->asm matching, filtering, or automatic recompile.
+
+Emacs 26 or the @code{cl-print} package are required.
+
+@node Common Lisp
+@section Common Lisp
+
+No support for source->asm matching or filtering. Only @code{sbcl} and 
@code{clisp}
+supported at the moment, with @code{sbcl} giving much better results.
+
+@node Developing
+@chapter Developing
+
+These are some tips which will help people working on developing or 
customizing RMSbolt.
+@menu
+* Adding a Language::
+@end menu
+
+@node Adding a Language
+@section Adding a Language
+
+Adding support for a new language is fairly easy. The closer it is to existing
+compilers, the easier it will be (to the point where a clone of a C compiler is
+just a couple copy-paste lines). However, it is not excessively hard to add
+support for completely foreign compilers and bytecode/assembly formats.
+
+As a minimum starting point, you must know how to compile a source file to
+assembly or bytecode on the command line, and know how the line numbers are
+available in the compiled form if they exist.
+
+@enumerate
+@item
+@uref{rmsbolt.el,Add a new entry to the language definitions statement.}
+@itemize
+@item
+To do this, you will need to (at a minimum) add a mode, compile-command, a
+compile-cmd-function, and a starter file name.
+@item
+The compile-cmd-function is a function that will turn local variable
+settings into a valid command which will take in a filename and output
+assembly or an executable. See @code{rmsbolt--c-compile-cmd} for an example.
+@item
+When building compilation commands, please make sure to use absolute paths,
+as the default-directory is not guaranteed to be stable.
+@item
+If the assembly is not in a standard format, you will need to define a
+@code{process-asm-custom-fn} as well (see python/java for examples).
+@item
+If you would like to add language tweaks in your own config (ie: take full
+control over what rmsbolt does completely), you can use
+@code{rmsbolt-language-descriptor} to fully override the defaults with a custom
+language definition.
+@end itemize
+@item
+@uref{rmsbolt.el,Add a new entry into the starter file}
+@itemize
+@item
+For this, you will need to make a starter file. See @uref{starters/,this 
folder} for
+existing examples.
+@item
+Ideally, try to pick something which is interesting to play with from an
+disassembly point of view.
+@end itemize
+@end enumerate
+
+You're done!
+
+@c Emacs 25.1.1 (Org mode 8.2.10)
+@bye
\ No newline at end of file