For golang/go#33955.

Change-Id: Iecef7537016b629311f67c42500e614ba60b107c
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222837
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>

For golang/go#33955.

Change-Id: I92c3c896055ed1baae34b0d85539068e6221ad38
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222838
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>

Wrapping long lines will make diffs easier to read
for the eventual conversion to Markdown.

For golang/go#33955.

Change-Id: Ibcc1b5a84ccc9144b5fcdc9266f2da3e2cf3c5a3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222839
Reviewed-by: Ian Lance Taylor <iant@golang.org>

A few articles used four spaces instead.
The present format will convert to four spaces for indentation on its own; use tabs.
The present format does not care what indentation is used, but use tabs everywhere for consistency.

For golang/go#33955.

Change-Id: I2bab8aa72fa2f68d48fb833b7317f87d7624a05f
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222840
Reviewed-by: Ian Lance Taylor <iant@golang.org>

Remove repeated blank lines, trailing spaces, trailing blank lines
Remove comments from survey2018.article (only article using them).
Remove blank lines between successive ".commands".

For golang/go#33955.

Change-Id: I90cae37a859a8e39549520569d5f10bc455415d3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222841
Reviewed-by: Ian Lance Taylor <iant@golang.org>

Also one missing "by".
This will make Markdown diffs sync better.
Otherwise there's a rewrite on nearly every line
and diff loses track of what matches what.

For golang/go#33955.

Change-Id: I65391a4c768d925797181af1e054373d38510600
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222842
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>

This is not strictly necessary, but being able to wrap these long lines
helps make the diffs for the Markdown conversion of old files easier to read.

The wrapping of the blog is in CL 222839.

For golang/go#33955.

Change-Id: I26c3f8db6b137c194f03b2538f221aa4fc3f2324
Reviewed-on: https://go-review.googlesource.com/c/tools/+/222843
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Rob Pike <r@golang.org>

I forgot to put in a section heading and every line
containing a colon in the text got parsed as a URL,
failing and printing errors. It took a while to find
where they were coming from.

For golang/go#33955.

Change-Id: Ibbc41a8446c292f6ab363829cf31fe594152e42d
Reviewed-on: https://go-review.googlesource.com/c/tools/+/222844
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Rob Pike <r@golang.org>

Commands like .code now have a TemplateCmd method
that returns the original command.

The Text struct now has a Raw field set when Pre==true.
It contains the original indented text, without the tab "fixing".

This helps building tooling that reformats or rewrites present files.

For golang/go#33955.

Change-Id: Ieb036e8b509a4531d120c597b19f2158306a5352
Reviewed-on: https://go-review.googlesource.com/c/tools/+/222845
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Rob Pike <r@golang.org>

Markdown is enabled by starting the title with "# ".
See the new documentation in present/doc.go for details.

For golang/go#33955.

Change-Id: I04ef2aa2cf253bdf48910c5674d679a482ffa33f
Reviewed-on: https://go-review.googlesource.com/c/tools/+/222846
Reviewed-by: Rob Pike <r@golang.org>

…bled present

Accepting Markdown in present is nice, but the job isn't done unless we
actually convert all our existing blog files to the new format. Otherwise we
have two different kinds of files to understand when working in that
directory. This tool lets us mechanically convert all the existing blog articles.

For golang/go#33955.

Change-Id: If8a8dd90eefa171f422644134d0571e2abe4c7cb
Reviewed-on: https://go-review.googlesource.com/c/tools/+/222847
Reviewed-by: Rob Pike <r@golang.org>

Converted blog to Markdown-enabled present (CL 222846)
using present2md (CL 222847).

For golang/go#33955.

Change-Id: Ib39fa1ddd9a46f9c7a62a2ca7b96e117635553e8
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222848
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>

Two backquote characters were expressed as 6 consecutive backquotes in
the legacy article format. That unusual sequence didn't translate well
into the new Markdown article format in CL 222848.
Replace it with simple HTML, since this is hard to express in Markdown.

For golang/go#33955.

Change-Id: I575aa89c9f9104de694d9a8dad4ca103cc4c1567
Reviewed-on: https://go-review.googlesource.com/c/blog/+/231817
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>

When indentation is used to create a code block immediately following
a list, Markdown syntax is ambiguous: it can be interpreted as another
text paragraph belonging to the last list entry, or as a standalone
code block.

The original behavior in CL 197637 made this unambiguously a code block
because the present format did not support lists. This changed when the
article was converted to use Markdown syntax in CL 222848.

Start using a fenced code block instead of indentation to resolve the
Markdown ambiguity and restore original behavior.

For golang/go#33955.

Change-Id: I9537bc72d7a32f90592942591b2688fb2f26c452
Reviewed-on: https://go-review.googlesource.com/c/blog/+/245017
Reviewed-by: Jean de Klerk <deklerk@google.com>

…line endings

For golang/go#33955.

Change-Id: Iecef7537016b629311f67c42500e614ba60b107c
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222837
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
X-Blog-Commit: f10b036ecb1362ffb4428bd9e02a99da4e7189a4

For golang/go#33955.

Change-Id: I92c3c896055ed1baae34b0d85539068e6221ad38
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222838
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
X-Blog-Commit: 0b4fcd39865e575704b5928c9a8f1cd21e18e8b2

Wrapping long lines will make diffs easier to read
for the eventual conversion to Markdown.

For golang/go#33955.

Change-Id: Ibcc1b5a84ccc9144b5fcdc9266f2da3e2cf3c5a3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222839
Reviewed-by: Ian Lance Taylor <iant@golang.org>
X-Blog-Commit: 482079d678d84e207dd9ae63266c4bd4e653886b

A few articles used four spaces instead.
The present format will convert to four spaces for indentation on its own; use tabs.
The present format does not care what indentation is used, but use tabs everywhere for consistency.

For golang/go#33955.

Change-Id: I2bab8aa72fa2f68d48fb833b7317f87d7624a05f
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222840
Reviewed-by: Ian Lance Taylor <iant@golang.org>
X-Blog-Commit: 9dd3d9b97af3dba2bd18f1a5e18bd8e8edf78962

Remove repeated blank lines, trailing spaces, trailing blank lines
Remove comments from survey2018.article (only article using them).
Remove blank lines between successive ".commands".

For golang/go#33955.

Change-Id: I90cae37a859a8e39549520569d5f10bc455415d3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222841
Reviewed-by: Ian Lance Taylor <iant@golang.org>
X-Blog-Commit: 7fd29cb024126de10a90c54427e050e7928c54b4

Also one missing "by".
This will make Markdown diffs sync better.
Otherwise there's a rewrite on nearly every line
and diff loses track of what matches what.

For golang/go#33955.

Change-Id: I65391a4c768d925797181af1e054373d38510600
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222842
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
X-Blog-Commit: 53cf23be3ddec2153847b84f09a9fce04bafa779

Converted blog to Markdown-enabled present (CL 222846)
using present2md (CL 222847).

For golang/go#33955.

Change-Id: Ib39fa1ddd9a46f9c7a62a2ca7b96e117635553e8
Reviewed-on: https://go-review.googlesource.com/c/blog/+/222848
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>
X-Blog-Commit: af5018f64e406aaa646dae066f28de57321ea5ce

Two backquote characters were expressed as 6 consecutive backquotes in
the legacy article format. That unusual sequence didn't translate well
into the new Markdown article format in CL 222848.
Replace it with simple HTML, since this is hard to express in Markdown.

For golang/go#33955.

Change-Id: I575aa89c9f9104de694d9a8dad4ca103cc4c1567
Reviewed-on: https://go-review.googlesource.com/c/blog/+/231817
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>
X-Blog-Commit: 10cc6f575bc85cafbda92aa7030a8e5c6e486dfe

When indentation is used to create a code block immediately following
a list, Markdown syntax is ambiguous: it can be interpreted as another
text paragraph belonging to the last list entry, or as a standalone
code block.

The original behavior in CL 197637 made this unambiguously a code block
because the present format did not support lists. This changed when the
article was converted to use Markdown syntax in CL 222848.

Start using a fenced code block instead of indentation to resolve the
Markdown ambiguity and restore original behavior.

For golang/go#33955.

Change-Id: I9537bc72d7a32f90592942591b2688fb2f26c452
Reviewed-on: https://go-review.googlesource.com/c/blog/+/245017
Reviewed-by: Jean de Klerk <deklerk@google.com>
X-Blog-Commit: fb994f42d8394e948c3d58235828e9ed5f2f3077