From 8e56412d7ad1af8b052789a871aa9a4c997cce16 Mon Sep 17 00:00:00 2001 From: k0pernicus Date: Thu, 19 May 2016 17:09:41 -0400 Subject: [PATCH 1/3] Add a table of contents --- readme.markdown | 121 ++++++++++++++++++++++++++++++++---------------- 1 file changed, 81 insertions(+), 40 deletions(-) diff --git a/readme.markdown b/readme.markdown index 70be1d3..041ae55 100644 --- a/readme.markdown +++ b/readme.markdown @@ -3,11 +3,51 @@ Nimble is a *beta*-grade *package manager* for the [Nim programming language](http://nim-lang.org). - Interested in learning **how to create a package**? Skip directly to that section [here](#creating-packages). -## Installation +## Contents + +* [Installation](#installation) + * [Unix](#installation_unix) + * [Windows](#installation_windows) + * [Using the pre-built archives](#inst_win_pre) + * [From source](#inst_win_source) +* [Nimble's folder structure and packages](#nimble_struct) +* [Nimble usage](#nimble_usage) + * [refresh](#nimble_refresh_u) + * [install](#nimble_install_u) + * [uninstall](#nimble_uninstall_u) + * [build](#nimble_build_u) + * [c](#nimble_c_u) + * [list](#nimble_list_u) + * [search](#nimble_search_u) + * [path](#nimble_path_u) + * [init](#nimble_init_u) + * [publish](#nimble_publish_u) + * [tasks](#nimble_tasks_u) + * [dump](#nimble_dump_u) +* [Configuration](#configuration) +* [Creating packages](#creating_packages) + * [Nimscript format](#nimscript_format) + * [Libraries](#libraries) + * [Binary packages](#binary_packages) + * [Hybrids](#hybrids) + * [Dependencies](#dependencies) + * [Nim compiler](#nim_compiler) + * [Versions](#versions) +* [Submitting your package to the package list](#submitting) +* [```.nimble``` reference](#nimble_reference) + * [\[Package\]](#package) + * [Required](#required) + * [Optional](#package_optional) + * [\[Dependencies\]](#deps) + * [Optional](#deps_optional) +* [Troubleshooting](#troubleshooting) +* [Contribution](#contribution) +* [About](#about) + +## Installation The latest version of Nimble (in the master branch) is primarily tested with the latest version of the Nim compiler (in the devel branch). You can be sure @@ -38,7 +78,7 @@ info. The following sections give platform-specific instructions on how to compile and install Nimble. -### Unix +### Unix On Unix-like operating systems Nimble can be compiled and installed with two simple @@ -55,14 +95,14 @@ in ``~/.nimble/bin``. You must then add ``~/.nimble/bin`` to your ``$PATH``. Updating nimble can then be done by executing ``nimble install nimble``. -### Windows +### Windows You can install Nimble via a pre-built installation archive which is available on the [releases](https://github.com/nim-lang/nimble/releases) page. Alternatively, you can also install Nimble from source, but the instructions for doing so are a bit different on Windows. -#### Using the pre-built archives +#### Using the pre-built archives Download the latest release archive from the [releases](https://github.com/nim-lang/nimble/releases) page. These archives @@ -74,7 +114,7 @@ One important thing to note is that this installation requires you have the Nim compiler in your PATH. Once the installation completes you should add ``C:\Users\YourName\.nimble\bin`` to your PATH. -#### From source +#### From source On Windows installing Nimble from source is slightly more complex: @@ -89,7 +129,8 @@ during installation Nimble recompiles itself causing an error. Once the installation completes you should add ``C:\Users\YourName\.nimble\bin`` to your PATH. -## Nimble's folder structure and packages +## Nimble's folder structure +and packages Nimble stores everything that has been installed in ``~/.nimble`` on Unix systems and in your ``$home/.nimble`` on Windows. Libraries are stored in @@ -102,12 +143,12 @@ However, some Nimble packages can provide additional tools or commands. If you don't add their location (``$nimbleDir/bin``) to your ``$PATH`` they will not work properly and you won't be able to run them. -## Nimble usage +## Nimble usage Once you have Nimble installed on your system you can run the ``nimble`` command to obtain a list of available commands. -### nimble refresh +### nimble refresh The ``refresh`` command is used to fetch and update the list of Nimble packages (see below). There is no automatic update mechanism, so you need to run this @@ -127,7 +168,7 @@ a third-party package list. Package lists can be specified in Nimble's config. Take a look at the config section below to see how to do this. -### nimble install +### nimble install The ``install`` command will download and install a package. You need to pass the name of the package (or packages) you want to install. If any of the @@ -170,7 +211,7 @@ list. See the [Creating Packages](#creating-packages) section for more info on t A URL to a repository can also be specified, Nimble will automatically detect the type of the repository that the url points to and install it. -### nimble uninstall +### nimble uninstall The ``uninstall`` command will remove an installed package. Attempting to remove a package which other packages depend on is disallowed and will result in an @@ -180,14 +221,14 @@ Similar to the ``install`` command you can specify a version range, for example: $ nimble uninstall nimgame@0.5 -### nimble build +### nimble build The ``build`` command is mostly used by developers who want to test building their ``.nimble`` package. This command will build the package in debug mode, without installing anything. The ``install`` command will build the package in release mode instead. -### nimble c +### nimble c The ``c`` (or ``compile``, ``js``, ``cc``, ``cpp``) command can be used by developers to compile individual modules inside their package. All options @@ -197,7 +238,7 @@ Nimble will use the backend specified in the package's ``.nimble`` file if the command ``c`` or ``compile`` is specified. The more specific ``js``, ``cc``, ``cpp`` can be used to override that. -### nimble list +### nimble list The ``list`` command will display the known list of packages available for Nimble. An optional ``--ver`` parameter can be specified to tell Nimble to @@ -205,7 +246,7 @@ query remote git repositories for the list of versions of the packages and to then print the versions. Please note however that this can be slow as each package must be queried separately. -### nimble search +### nimble search If you don't want to go through the whole output of the ``list`` command you can use the ``search`` command specifying as parameters the package name and/or @@ -233,7 +274,7 @@ query remote git repositories for the list of versions of the packages and to then print the versions. Please note however that this can be slow as each package must be queried separately. -### nimble path +### nimble path The nimble ``path`` command will show the absolute path to the installed packages matching the specified parameters. Since there can be many versions of @@ -251,7 +292,7 @@ which can be useful to read the bundled documentation. Example: $ cd `nimble path argument_parser` $ less README.md -### nimble init +### nimble init The nimble ``init`` command will start a simple wizard which will create a quick ``.nimble`` file for your project. @@ -260,25 +301,25 @@ As of version 0.7.0, the ``.nimble`` file that this command creates will use the new NimScript format. Check out the [Creating Packages](#creating-packages) section for more info. -### nimble publish +### nimble publish Publishes your Nimble package to the official Nimble package repository. **Note:** Requires a valid Github account. -### nimble tasks +### nimble tasks For a nimble package in the current working directory, list the tasks which that package defines. This is only supported for packages utilising the new nimscript .nimble files. -### nimble dump +### nimble dump Outputs information about the package in the current working directory in an ini-compatible format. Useful for tools wishing to read metadata about Nimble packages who do not want to use the NimScript evaluator. -## Configuration +## Configuration At startup Nimble will attempt to read ``~/.config/nimble/nimble.ini`` on Linux (on Windows it will attempt to read @@ -317,7 +358,7 @@ You can currently configure the following in this file: environment variables. **Default: ""** -## Creating Packages +## Creating Packages Nimble works on git repositories as its primary source of packages. Its list of packages is stored in a JSON file which is freely accessible in the @@ -361,7 +402,7 @@ Nimble currently supports installation of packages from a local directory, a git repository and a mercurial repository. The .nimble file must be present in the root of the directory or repository being installed. -### The new NimScript format +### The new NimScript format **Warning:** This feature is still very experimental. You are encouraged to try it, but be aware that it may change significantly in the future or @@ -443,7 +484,7 @@ also return ``false`` from these blocks to stop further execution. The ``nimscriptapi.nim`` module specifies this and includes other definitions which are also useful. Take a look at it for more information. -### Libraries +### Libraries Library packages are likely the most popular form of Nimble packages. They are meant to be used by other library packages or the ultimate binary packages. @@ -483,7 +524,7 @@ Directories and files can also be specified on a *whitelist* basis, if you specify either of ``InstallDirs``, ``InstallFiles`` or ``InstallExt`` then Nimble will **only** install the files specified. -### Binary packages +### Binary packages These are application packages which require building prior to installation. A package is automatically a binary package as soon as it sets at least one @@ -509,7 +550,7 @@ package you should ensure that the dependencies you specified are correct. You can do this by running ``nimble build`` or ``nimble install`` in the directory of your package. -### Hybrids +### Hybrids One thing to note about library and binary package hybrids is that your binary may share the name of the package. This will mean that you will @@ -521,7 +562,7 @@ The current convention to get around this problem is to append ``pkg`` to the name as is done for nimble. -### Dependencies +### Dependencies Dependencies are specified under the ``[Deps]`` section in a nimble file. The ``requires`` key field is used to specify them. For example: @@ -548,7 +589,7 @@ These have to be concrete however. This is done with the ``#`` character, for example: ``jester#head``. Which will make your package depend on the latest commit of Jester. -### Nim compiler +### Nim compiler The Nim compiler cannot read .nimble files. Its knowledge of Nimble is limited to the ``nimblePaths`` feature which allows it to use packages installed @@ -564,7 +605,7 @@ This means that you can safely compile using the compiler when developing your software, but you should use nimble to build the package before publishing it to ensure that the dependencies you specified are correct. -### Versions +### Versions Versions of cloned packages via git or mercurial are determined through the repository's *tags*. @@ -580,17 +621,17 @@ package after checking out the latest version. You can force the installation of the HEAD of the repository by specifying ``#head`` after the package name in your dependency list. -## Submitting your package to the package list. +## Submitting your package to the package list Nimble's packages list is stored on github and everyone is encouraged to add their own packages to it! Take a look at [nim-lang/packages](https://github.com/nim-lang/packages) to learn more. -## .nimble reference +## ```.nimble``` reference -### [Package] +### [Package] -#### Required +#### Required * ``name`` - The name of the package. *(This is not required in the new NimScript format)* * ``version`` - The *current* version of this package. This should be incremented @@ -599,7 +640,7 @@ their own packages to it! Take a look at * ``description`` - A string describing the package. * ``license`` - The name of the license in which this package is licensed under. -#### Optional +#### Optional * ``SkipDirs`` - A list of directory names which should be skipped during installation, separated by commas. @@ -636,25 +677,25 @@ their own packages to it! Take a look at ``js``. **Default**: c -### [Deps]/[Dependencies] +### [Deps]/[Dependencies] -#### Optional +#### Optional * ``requires`` - Specified a list of package names with an optional version range separated by commas. **Example**: ``nim >= 0.10.0, jester``; with this value your package will depend on ``nim`` version 0.10.0 or greater and on any version of ``jester``. -## Troubleshooting +## Troubleshooting -* "SSL support is not available. Cannot connect over SSL. [HttpRequestError]" +* ```SSL support is not available. Cannot connect over SSL. [HttpRequestError]``` Make sure that nimble is configured to run with SSL, adding a ```-d:ssl``` flag to the file ```src/nimble.nim.cfg```. After that, you can run ```src/nimble install``` and overwrite the existing installation. -## Contribution +## Contribution If you would like to help, feel free to fork and make any additions you see fit and then send a pull request. @@ -663,7 +704,7 @@ If you have any questions about the project you can ask me directly on github, ask on the Nim [forum](http://forum.nim-lang.org), or ask on Freenode in the #nim channel. -## About +## About Nimble has been written by [Dominik Picheta](http://picheta.me/) with help from a number of From 977475c9a61d489253b8dd01bc7ad2e0a1b3d384 Mon Sep 17 00:00:00 2001 From: k0pernicus Date: Thu, 19 May 2016 17:19:28 -0400 Subject: [PATCH 2/3] Add new format from markdown-toc --- readme.markdown | 157 ++++++++++++++++++++++++------------------------ 1 file changed, 78 insertions(+), 79 deletions(-) diff --git a/readme.markdown b/readme.markdown index 041ae55..9dc977f 100644 --- a/readme.markdown +++ b/readme.markdown @@ -4,50 +4,50 @@ Nimble is a *beta*-grade *package manager* for the [Nim programming language](http://nim-lang.org). Interested in learning **how to create a package**? Skip directly to that section -[here](#creating-packages). +[here](#creating-packages). -## Contents +- [Installation](#installation) + - [Unix](#unix) + - [Windows](#windows) + - [Using the pre-built archives](#using-the-pre-built-archives) + - [From source](#from-source) +- [Nimble's folder structure and packages](#nimbles-folder-structure-and-packages) +- [Nimble usage](#nimble-usage) + - [nimble refresh](#nimble-refresh) + - [nimble install](#nimble-install) + - [nimble uninstall](#nimble-uninstall) + - [nimble build](#nimble-build) + - [nimble c](#nimble-c) + - [nimble list](#nimble-list) + - [nimble search](#nimble-search) + - [nimble path](#nimble-path) + - [nimble init](#nimble-init) + - [nimble publish](#nimble-publish) + - [nimble tasks](#nimble-tasks) + - [nimble dump](#nimble-dump) +- [Configuration](#configuration) +- [Creating Packages](#creating-packages) + - [The new NimScript format](#the-new-nimscript-format) + - [Libraries](#libraries) + - [Binary packages](#binary-packages) + - [Hybrids](#hybrids) + - [Dependencies](#dependencies) + - [Nim compiler](#nim-compiler) + - [Versions](#versions) +- [Submitting your package to the package list.](#submitting-your-package-to-the-package-list) +- [.nimble reference](#nimble-reference) + - [[Package]](#package) + - [Required](#required) + - [Optional](#optional) + - [[Deps]/[Dependencies]](#depsdependencies) + - [Optional](#optional) +- [Troubleshooting](#troubleshooting) +- [Contribution](#contribution) +- [About](#about) -* [Installation](#installation) - * [Unix](#installation_unix) - * [Windows](#installation_windows) - * [Using the pre-built archives](#inst_win_pre) - * [From source](#inst_win_source) -* [Nimble's folder structure and packages](#nimble_struct) -* [Nimble usage](#nimble_usage) - * [refresh](#nimble_refresh_u) - * [install](#nimble_install_u) - * [uninstall](#nimble_uninstall_u) - * [build](#nimble_build_u) - * [c](#nimble_c_u) - * [list](#nimble_list_u) - * [search](#nimble_search_u) - * [path](#nimble_path_u) - * [init](#nimble_init_u) - * [publish](#nimble_publish_u) - * [tasks](#nimble_tasks_u) - * [dump](#nimble_dump_u) -* [Configuration](#configuration) -* [Creating packages](#creating_packages) - * [Nimscript format](#nimscript_format) - * [Libraries](#libraries) - * [Binary packages](#binary_packages) - * [Hybrids](#hybrids) - * [Dependencies](#dependencies) - * [Nim compiler](#nim_compiler) - * [Versions](#versions) -* [Submitting your package to the package list](#submitting) -* [```.nimble``` reference](#nimble_reference) - * [\[Package\]](#package) - * [Required](#required) - * [Optional](#package_optional) - * [\[Dependencies\]](#deps) - * [Optional](#deps_optional) -* [Troubleshooting](#troubleshooting) -* [Contribution](#contribution) -* [About](#about) + -## Installation +## Installation The latest version of Nimble (in the master branch) is primarily tested with the latest version of the Nim compiler (in the devel branch). You can be sure @@ -78,7 +78,7 @@ info. The following sections give platform-specific instructions on how to compile and install Nimble. -### Unix +### Unix On Unix-like operating systems Nimble can be compiled and installed with two simple @@ -95,14 +95,14 @@ in ``~/.nimble/bin``. You must then add ``~/.nimble/bin`` to your ``$PATH``. Updating nimble can then be done by executing ``nimble install nimble``. -### Windows +### Windows You can install Nimble via a pre-built installation archive which is available on the [releases](https://github.com/nim-lang/nimble/releases) page. Alternatively, you can also install Nimble from source, but the instructions for doing so are a bit different on Windows. -#### Using the pre-built archives +#### Using the pre-built archives Download the latest release archive from the [releases](https://github.com/nim-lang/nimble/releases) page. These archives @@ -114,7 +114,7 @@ One important thing to note is that this installation requires you have the Nim compiler in your PATH. Once the installation completes you should add ``C:\Users\YourName\.nimble\bin`` to your PATH. -#### From source +#### From source On Windows installing Nimble from source is slightly more complex: @@ -129,8 +129,7 @@ during installation Nimble recompiles itself causing an error. Once the installation completes you should add ``C:\Users\YourName\.nimble\bin`` to your PATH. -## Nimble's folder structure -and packages +## Nimble's folder structure and packages Nimble stores everything that has been installed in ``~/.nimble`` on Unix systems and in your ``$home/.nimble`` on Windows. Libraries are stored in @@ -143,12 +142,12 @@ However, some Nimble packages can provide additional tools or commands. If you don't add their location (``$nimbleDir/bin``) to your ``$PATH`` they will not work properly and you won't be able to run them. -## Nimble usage +## Nimble usage Once you have Nimble installed on your system you can run the ``nimble`` command to obtain a list of available commands. -### nimble refresh +### nimble refresh The ``refresh`` command is used to fetch and update the list of Nimble packages (see below). There is no automatic update mechanism, so you need to run this @@ -168,7 +167,7 @@ a third-party package list. Package lists can be specified in Nimble's config. Take a look at the config section below to see how to do this. -### nimble install +### nimble install The ``install`` command will download and install a package. You need to pass the name of the package (or packages) you want to install. If any of the @@ -211,7 +210,7 @@ list. See the [Creating Packages](#creating-packages) section for more info on t A URL to a repository can also be specified, Nimble will automatically detect the type of the repository that the url points to and install it. -### nimble uninstall +### nimble uninstall The ``uninstall`` command will remove an installed package. Attempting to remove a package which other packages depend on is disallowed and will result in an @@ -221,14 +220,14 @@ Similar to the ``install`` command you can specify a version range, for example: $ nimble uninstall nimgame@0.5 -### nimble build +### nimble build The ``build`` command is mostly used by developers who want to test building their ``.nimble`` package. This command will build the package in debug mode, without installing anything. The ``install`` command will build the package in release mode instead. -### nimble c +### nimble c The ``c`` (or ``compile``, ``js``, ``cc``, ``cpp``) command can be used by developers to compile individual modules inside their package. All options @@ -238,7 +237,7 @@ Nimble will use the backend specified in the package's ``.nimble`` file if the command ``c`` or ``compile`` is specified. The more specific ``js``, ``cc``, ``cpp`` can be used to override that. -### nimble list +### nimble list The ``list`` command will display the known list of packages available for Nimble. An optional ``--ver`` parameter can be specified to tell Nimble to @@ -246,7 +245,7 @@ query remote git repositories for the list of versions of the packages and to then print the versions. Please note however that this can be slow as each package must be queried separately. -### nimble search +### nimble search If you don't want to go through the whole output of the ``list`` command you can use the ``search`` command specifying as parameters the package name and/or @@ -274,7 +273,7 @@ query remote git repositories for the list of versions of the packages and to then print the versions. Please note however that this can be slow as each package must be queried separately. -### nimble path +### nimble path The nimble ``path`` command will show the absolute path to the installed packages matching the specified parameters. Since there can be many versions of @@ -292,7 +291,7 @@ which can be useful to read the bundled documentation. Example: $ cd `nimble path argument_parser` $ less README.md -### nimble init +### nimble init The nimble ``init`` command will start a simple wizard which will create a quick ``.nimble`` file for your project. @@ -301,25 +300,25 @@ As of version 0.7.0, the ``.nimble`` file that this command creates will use the new NimScript format. Check out the [Creating Packages](#creating-packages) section for more info. -### nimble publish +### nimble publish Publishes your Nimble package to the official Nimble package repository. **Note:** Requires a valid Github account. -### nimble tasks +### nimble tasks For a nimble package in the current working directory, list the tasks which that package defines. This is only supported for packages utilising the new nimscript .nimble files. -### nimble dump +### nimble dump Outputs information about the package in the current working directory in an ini-compatible format. Useful for tools wishing to read metadata about Nimble packages who do not want to use the NimScript evaluator. -## Configuration +## Configuration At startup Nimble will attempt to read ``~/.config/nimble/nimble.ini`` on Linux (on Windows it will attempt to read @@ -358,7 +357,7 @@ You can currently configure the following in this file: environment variables. **Default: ""** -## Creating Packages +## Creating Packages Nimble works on git repositories as its primary source of packages. Its list of packages is stored in a JSON file which is freely accessible in the @@ -402,7 +401,7 @@ Nimble currently supports installation of packages from a local directory, a git repository and a mercurial repository. The .nimble file must be present in the root of the directory or repository being installed. -### The new NimScript format +### The new NimScript format **Warning:** This feature is still very experimental. You are encouraged to try it, but be aware that it may change significantly in the future or @@ -484,7 +483,7 @@ also return ``false`` from these blocks to stop further execution. The ``nimscriptapi.nim`` module specifies this and includes other definitions which are also useful. Take a look at it for more information. -### Libraries +### Libraries Library packages are likely the most popular form of Nimble packages. They are meant to be used by other library packages or the ultimate binary packages. @@ -524,7 +523,7 @@ Directories and files can also be specified on a *whitelist* basis, if you specify either of ``InstallDirs``, ``InstallFiles`` or ``InstallExt`` then Nimble will **only** install the files specified. -### Binary packages +### Binary packages These are application packages which require building prior to installation. A package is automatically a binary package as soon as it sets at least one @@ -550,7 +549,7 @@ package you should ensure that the dependencies you specified are correct. You can do this by running ``nimble build`` or ``nimble install`` in the directory of your package. -### Hybrids +### Hybrids One thing to note about library and binary package hybrids is that your binary may share the name of the package. This will mean that you will @@ -562,7 +561,7 @@ The current convention to get around this problem is to append ``pkg`` to the name as is done for nimble. -### Dependencies +### Dependencies Dependencies are specified under the ``[Deps]`` section in a nimble file. The ``requires`` key field is used to specify them. For example: @@ -589,7 +588,7 @@ These have to be concrete however. This is done with the ``#`` character, for example: ``jester#head``. Which will make your package depend on the latest commit of Jester. -### Nim compiler +### Nim compiler The Nim compiler cannot read .nimble files. Its knowledge of Nimble is limited to the ``nimblePaths`` feature which allows it to use packages installed @@ -605,7 +604,7 @@ This means that you can safely compile using the compiler when developing your software, but you should use nimble to build the package before publishing it to ensure that the dependencies you specified are correct. -### Versions +### Versions Versions of cloned packages via git or mercurial are determined through the repository's *tags*. @@ -621,17 +620,17 @@ package after checking out the latest version. You can force the installation of the HEAD of the repository by specifying ``#head`` after the package name in your dependency list. -## Submitting your package to the package list +## Submitting your package to the package list. Nimble's packages list is stored on github and everyone is encouraged to add their own packages to it! Take a look at [nim-lang/packages](https://github.com/nim-lang/packages) to learn more. -## ```.nimble``` reference +## .nimble reference -### [Package] +### [Package] -#### Required +#### Required * ``name`` - The name of the package. *(This is not required in the new NimScript format)* * ``version`` - The *current* version of this package. This should be incremented @@ -640,7 +639,7 @@ their own packages to it! Take a look at * ``description`` - A string describing the package. * ``license`` - The name of the license in which this package is licensed under. -#### Optional +#### Optional * ``SkipDirs`` - A list of directory names which should be skipped during installation, separated by commas. @@ -677,16 +676,16 @@ their own packages to it! Take a look at ``js``. **Default**: c -### [Deps]/[Dependencies] +### [Deps]/[Dependencies] -#### Optional +#### Optional * ``requires`` - Specified a list of package names with an optional version range separated by commas. **Example**: ``nim >= 0.10.0, jester``; with this value your package will depend on ``nim`` version 0.10.0 or greater and on any version of ``jester``. -## Troubleshooting +## Troubleshooting * ```SSL support is not available. Cannot connect over SSL. [HttpRequestError]``` @@ -695,7 +694,7 @@ flag to the file ```src/nimble.nim.cfg```. After that, you can run ```src/nimble install``` and overwrite the existing installation. -## Contribution +## Contribution If you would like to help, feel free to fork and make any additions you see fit and then send a pull request. @@ -704,7 +703,7 @@ If you have any questions about the project you can ask me directly on github, ask on the Nim [forum](http://forum.nim-lang.org), or ask on Freenode in the #nim channel. -## About +## About Nimble has been written by [Dominik Picheta](http://picheta.me/) with help from a number of From 831dfaec0b5199d00bc01a0cd6ce31af2cdad269 Mon Sep 17 00:00:00 2001 From: k0pernicus Date: Thu, 19 May 2016 17:20:28 -0400 Subject: [PATCH 3/3] Fix typo and add title --- readme.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/readme.markdown b/readme.markdown index 9dc977f..16e6c69 100644 --- a/readme.markdown +++ b/readme.markdown @@ -4,7 +4,9 @@ Nimble is a *beta*-grade *package manager* for the [Nim programming language](http://nim-lang.org). Interested in learning **how to create a package**? Skip directly to that section -[here](#creating-packages). +[here](#creating-packages). + +## Contents - [Installation](#installation) - [Unix](#unix) @@ -45,8 +47,6 @@ Interested in learning **how to create a package**? Skip directly to that sectio - [Contribution](#contribution) - [About](#about) - - ## Installation The latest version of Nimble (in the master branch) is primarily tested with