1
0
mirror of https://github.com/adambard/learnxinyminutes-docs.git synced 2025-01-17 21:49:22 +01:00
Isaac Virshup 2df3917975
[RST/en] Fix compile errors from link and escaping
There were two issues here:

* The non-inline link was used incorrectly, and should have a colon after the specifier. 
* A compile error was generated from having a non-escaped `*`.

These can be verified by running `rst2html`:

```sh
$ rst2html.py ./restructuredtext.rst tmp.html
./restructuredtext.rst:24: (WARNING/2) Inline emphasis start-string without end-string.
./restructuredtext.rst:59: (WARNING/2) malformed hyperlink target.
```

After adding the colon, and adding the escape

```sh
$ rst2html.py ./restructuredtext.rst tmp.html
$
```

I've also added a sentence on escaping.
2020-06-24 16:55:02 +10:00
2018-10-24 22:42:04 +05:30
2019-09-22 23:33:55 +05:30
2020-02-28 10:19:01 -03:00
2020-02-13 10:38:29 +10:30
2016-06-26 14:33:01 +02:00
2020-03-24 20:44:47 +09:00
2020-05-26 18:45:43 -07:00
2019-11-01 13:52:16 +01:00
2017-08-25 13:50:47 +05:45
2020-02-13 10:38:29 +10:30
2020-02-13 10:38:29 +10:30
2020-02-13 22:09:07 -08:00
2017-10-09 08:04:01 +02:00
2017-11-06 18:34:48 +05:45
2020-02-13 10:38:29 +10:30
2018-08-30 19:10:56 -07:00
2016-03-14 12:38:47 +05:30
2020-02-13 10:38:29 +10:30
2015-10-07 23:11:24 -04:00
2020-05-26 18:13:38 -07:00
2019-08-01 16:45:11 +05:30
2018-03-14 08:40:50 +05:45
2020-02-21 18:46:28 -07:00
2020-05-23 15:34:40 -07:00
2019-04-06 00:03:34 +05:30
2018-02-28 17:01:12 +05:45
2019-11-26 14:11:46 +01:00
2020-02-06 17:37:13 +05:30
2020-01-31 02:06:48 +05:30
2019-08-03 17:06:50 +05:30
2018-10-23 20:36:28 -07:00
2013-06-29 20:19:14 -07:00
2017-10-16 14:32:51 +08:00
2017-08-23 10:14:39 +02:00
2017-03-21 18:19:49 -07:00
2018-10-20 21:11:17 +05:30
2020-02-27 11:50:39 +00:00
2017-08-23 10:14:39 +02:00
2019-11-04 11:05:21 -06:00
2019-09-29 23:29:13 -04:00
2017-05-25 14:29:39 +02:00
2018-10-15 23:22:14 -04:00
2017-08-23 10:14:39 +02:00
2018-06-02 17:46:37 +05:45
2020-02-13 10:38:29 +10:30
2018-10-20 21:30:06 +05:30
2018-11-12 21:14:08 +02:00
2020-05-21 00:52:38 -06:00
2020-01-23 19:57:30 -05:00
2019-08-05 14:31:01 +05:30
2020-05-24 14:08:31 -07:00
2017-08-18 10:12:58 -07:00
2019-02-13 11:06:16 +01:00
2018-08-31 12:13:02 +08:00
2019-01-09 17:10:06 -08:00
2018-10-14 12:40:30 +05:30
2020-02-25 19:13:42 +05:30
2013-06-29 03:38:34 -04:00
2020-01-22 13:49:33 +03:00
2014-12-22 13:26:30 +01:00
2019-06-13 13:10:53 -04:00
2016-10-23 14:24:50 +02:00
2019-02-28 18:40:00 +05:30
2018-12-03 22:30:37 +01:00
2016-11-09 22:31:46 -08:00
2019-11-15 22:53:36 -05:00
2018-11-26 09:56:09 +01:00
2020-02-12 21:25:39 +01:00
2020-06-04 19:59:09 -07:00
2017-08-23 10:14:39 +02:00
2019-10-12 20:25:05 +05:30
2019-01-10 17:07:51 +05:30
2018-10-22 20:59:56 -05:00
2019-08-08 22:16:37 +05:30
2020-02-02 17:56:16 +01:00
2019-03-13 23:03:26 +03:00
2020-04-05 01:12:31 +03:00
2019-07-02 10:13:37 +08:00
2020-02-13 10:38:29 +10:30

Learn X in Y minutes

Build Status

Whirlwind tours of (several, hopefully many someday) popular and ought-to-be-more-popular programming languages, presented as valid, commented code and explained as they go.

We need YOU!...

... to write more inline code tutorials. Just grab an existing file from this repo and copy the formatting (don't worry, it's all very simple). Make a new file, send a pull request, and if it passes muster I'll get it up pronto. Remember to fill in the "contributors" fields so you get credited properly!

Contributing

All contributions are welcome, from the tiniest typo to a brand new article. Translations in all languages are welcome (or, for that matter, original articles in any language). Send a pull request or open an issue any time of day or night.

Please prepend the tag [language/lang-code] to your issues and pull requests. For example, [python/en] for English Python. This will help everyone pick out things they care about.

We're happy for any contribution in any form, but if you're making more than one major change (i.e. translations for two different languages) it would be super cool of you to make a separate pull request for each one so that someone can review them more effectively and/or individually.

For a detailed style guide, please review the full CONTRIBUTING guidelines.

License

Contributors retain copyright to their work, and can request removal at any time. By uploading a doc here, you agree to publish your work under the default Creative Commons Attribution-ShareAlike 3.0 Unported licensing included on each doc page.

Anything not covered by the above -- basically, this README -- you can use as you wish, I guess.

Description
No description provided
Readme 78 MiB
Languages
Markdown 100%