about summary refs log tree commit diff
path: root/src/doc/tutorial.md
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2014-03-11 12:36:58 -0700
committerbors <bors@rust-lang.org>2014-03-11 12:36:58 -0700
commit74bfa7108a62c053fdeae2bb093f8035e19e2ef2 (patch)
tree4b447bfb82b4b87415087f7b71a5dd5c2b9e4ef0 /src/doc/tutorial.md
parent3bede9fd310540a0fd72371008f8aa606b23b11b (diff)
parent840a2701accbaeb6d4537db79e47150313c74d42 (diff)
downloadrust-74bfa7108a62c053fdeae2bb093f8035e19e2ef2.tar.gz
rust-74bfa7108a62c053fdeae2bb093f8035e19e2ef2.zip
auto merge of #12783 : adrientetar/rust/more-docs, r=alexcrichton
- remove `node.js` dep., it has no effect as of #12747 (1)
- switch between LaTeX compilers, some cleanups
- CSS: fixup the print stylesheet, refactor highlighting code (2)

(1): `prep.js` outputs its own HTML directives, which `pandoc` cannot recognize when converting the document into LaTeX (this is why the PDF docs have never been highlighted as of now).

Note that if we were to add the `.rust` class to snippets, we could probably use pandoc's native highlighting capatibilities i.e. Kate ([here is](http://adrientetar.github.io/rust-tuts/tutorial/tutorial.pdf) an example of that).

(2): the only real highlighting change is for lifetimes which are now brown instead of red, the rest is just refactor of twos shades of red that look the same.
Also I made numbers highlighting for src in rustdoc a tint more clear so that it is less bothering.

@alexcrichton, @huonw

Closes #9873. Closes #12788.
Diffstat (limited to 'src/doc/tutorial.md')
-rw-r--r--src/doc/tutorial.md9
1 files changed, 3 insertions, 6 deletions
diff --git a/src/doc/tutorial.md b/src/doc/tutorial.md
index d103b9356d9..de3f39ef81d 100644
--- a/src/doc/tutorial.md
+++ b/src/doc/tutorial.md
@@ -57,7 +57,7 @@ they don't contain references to names that aren't actually defined.
 
 # Getting started
 
-> **WARNING**: The tarball and installer links are for the most recent
+> ***Warning:*** The tarball and installer links are for the most recent
 > release, not master. To use master, you **must** build from [git].
 
 The Rust compiler currently must be built from a [tarball] or [git], unless
@@ -80,13 +80,10 @@ You may find that other platforms work, but these are our "tier 1"
 supported build environments that are most likely to work.
 
 > ***Note:*** Windows users should read the detailed
-> "[getting started][wiki-start]" notes on the wiki. Even when using
+> [Getting started][wiki-start] notes on the wiki. Even when using
 > the binary installer, the Windows build requires a MinGW installation,
-> the precise details of which are not discussed here. Finally, `rustc` may
-> need to be [referred to as `rustc.exe`][bug-3319]. It's a bummer, we
-> know.
+> the precise details of which are not discussed here.
 
-[bug-3319]: https://github.com/mozilla/rust/issues/3319
 [wiki-start]: https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust
 [git]: https://github.com/mozilla/rust.git