Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: more formatting fixes #7727

Merged
merged 5 commits into from
Aug 4, 2016
Merged

doc: more formatting fixes #7727

merged 5 commits into from
Aug 4, 2016

Conversation

ChALkeR
Copy link
Member

@ChALkeR ChALkeR commented Jul 14, 2016

Checklist
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

doc

Description of change

More or less a continuation of #7637.

Fixes some documentation formatting issues, this time split into separate commits (I can squash them, though).

  • Convert all instances if tab indentation in *.md files to spaces. This affects only three files — archive and 0.10 changelogs and one CTC meeting.
  • Language specification in the top-level *.md files code blocks.
  • Change the very top heading style in the README.md to be consistent with all the other headings (no visual change).
  • Remove extra two spaces indentation which was somewhy present in the iojs changelog for versions from v1.8.1 to v3.3.1 (last). It is not present in other changelogs and was not present before v1.8.1.
  • Minor fixes in the benchmark dir — specify language for code blocks, move definitions to the bottom.

/cc @nodejs/documentation, @addaleax, @silverwind

@ChALkeR ChALkeR added the doc Issues and PRs related to the documentations. label Jul 14, 2016
@ChALkeR ChALkeR changed the title More doc fixes doc: more formatting fixes Jul 14, 2016
@@ -28,7 +28,7 @@ On FreeBSD and OpenBSD, you may also need:
* libexecinfo (FreeBSD and OpenBSD only)


```text
```sh
Copy link
Contributor

@Fishrock123 Fishrock123 Jul 14, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

@ChALkeR ChALkeR Jul 14, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Fishrock123 Ah, previous commit merged with «sh». There is no difference though — you could use the file extension here, as js vs javascript and md vs markdown.

Should I change it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep these are all aliases. I'd prefer we keep it sh for simplicity.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This probably should be console, but I need to re-check the code highlighting on that.

@ChALkeR
Copy link
Member Author

ChALkeR commented Jul 14, 2016

Added fixes for the benchmark dir. /cc @mscdex

assumed you know what you're doing since you're specifically asking to use
these methods.
Timothy J Fontaine, Alexis Campailla)
This is a behavior change, by default we will not allow the negotiation to
Copy link
Member Author

@ChALkeR ChALkeR Jul 14, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw, the way it currently renders isn't nice:

  • crypto: Disable autonegotiation for SSLv2/3 by default (Fedor Indutny,
    Timothy J Fontaine, Alexis Campailla)
    This is a behavior change, by default we will not allow the negotiation to
    SSLv2 or SSLv3. If you want this behavior, run Node.js with either
    --enable-ssl2 or --enable-ssl3 respectively.
    This does not change the behavior for users specifically requesting
    SSLv2_method or SSLv3_method. While this behavior is not advised, it is
    assumed you know what you're doing since you're specifically asking to use
    these methods.

Perhaps split this into three paragraphs, i.e

  • crypto: Disable autonegotiation for SSLv2/3 by default (Fedor Indutny,
    Timothy J Fontaine, Alexis Campailla)

    This is a behavior change, by default we will not allow the negotiation to
    SSLv2 or SSLv3. If you want this behavior, run Node.js with either
    --enable-ssl2 or --enable-ssl3 respectively.

    This does not change the behavior for users specifically requesting
    SSLv2_method or SSLv3_method. While this behavior is not advised, it is
    assumed you know what you're doing since you're specifically asking to use
    these methods.

Opinions?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Splitting these into paragraphs sounds like a good idea to me.

@ChALkeR
Copy link
Member Author

ChALkeR commented Aug 4, 2016

I will rebase this once #7971 lands.

Upd: On a second thought, I will just exclude Readme changes =).

@ChALkeR
Copy link
Member Author

ChALkeR commented Aug 4, 2016

Rebased. I did not include the shconsole changes in the docs dir, those should not be blocking this and could be filed in another PR.

Dropped the Readme changes in favour of #7971, which covers more issues.

/cc @Trott, @nodejs/documentation

@Trott
Copy link
Member

Trott commented Aug 4, 2016

LGTM

1 similar comment
@targos
Copy link
Member

targos commented Aug 4, 2016

LGTM

ChALkeR added a commit that referenced this pull request Aug 4, 2016
* Add language specification for the txt code blocks.
* Move the definitions to the bottom.

Ref: #7727
@jasnell
Copy link
Member

jasnell commented Aug 4, 2016

LGTM

Convert all instances of tab indentation in *.md files to spaces.
This affects only three files.

PR-URL: nodejs#7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Continuing what a58b48b did for the
doc/ dir, this fixes some formatting issues in the *.md files that
are placed directly in the top-level directory.

README.md changes are excluded as they are covered by
nodejs#7971

Refs: nodejs#7637
PR-URL: nodejs#7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
This removes the extra two spaces indentation which was somewhy present
in the iojs changelog from v1.8.1 to v3.3.1.

iojs changelog was the only file affected.

PR-URL: nodejs#7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
* Add language specification for the txt code blocks.
* Move the definitions to the bottom.

Ref: nodejs#7727

PR-URL: nodejs#7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
This splits one huge commit description into paragraphs, which
supposedly was the intended behavior there.

PR-URL: nodejs#7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@ChALkeR ChALkeR merged commit e1643cc into nodejs:master Aug 4, 2016
@ChALkeR
Copy link
Member Author

ChALkeR commented Aug 4, 2016

Landed in 7400a4a...e1643cc.

ChALkeR added a commit to ChALkeR/io.js that referenced this pull request Aug 7, 2016
Specifies the configuration for remark-lint, a markdown linter.

This configuration does not cause any warnings on any of the currently
present *.md files (ignoring thirdparty).

It is useful not only for possible future tooling that would check the
markdown files syntax, but also as a configuration for editor plugins,
e.g. linter-markdown for atom-linter.

Refs: nodejs#7637
Refs: nodejs#7727
Refs: nodejs#7757
PR-URL: nodejs#7729
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Robert Jefe Lindstaedt <[email protected]>
@cjihrig cjihrig mentioned this pull request Aug 8, 2016
@cjihrig
Copy link
Contributor

cjihrig commented Aug 10, 2016

@ChALkeR could you backport commit f3f5a89 only. It doesn't apply cleanly, and it appears that the benchmarking README has gotten pretty out of sync with the one in master.

cjihrig pushed a commit that referenced this pull request Aug 10, 2016
Convert all instances of tab indentation in *.md files to spaces.
This affects only three files.

PR-URL: #7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
cjihrig pushed a commit that referenced this pull request Aug 10, 2016
Continuing what a58b48b did for the
doc/ dir, this fixes some formatting issues in the *.md files that
are placed directly in the top-level directory.

README.md changes are excluded as they are covered by
#7971

Refs: #7637
PR-URL: #7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
cjihrig pushed a commit that referenced this pull request Aug 10, 2016
This removes the extra two spaces indentation which was somewhy present
in the iojs changelog from v1.8.1 to v3.3.1.

iojs changelog was the only file affected.

PR-URL: #7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
cjihrig pushed a commit that referenced this pull request Aug 10, 2016
This splits one huge commit description into paragraphs, which
supposedly was the intended behavior there.

PR-URL: #7727
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: James M Snell <[email protected]>
cjihrig pushed a commit that referenced this pull request Aug 10, 2016
Specifies the configuration for remark-lint, a markdown linter.

This configuration does not cause any warnings on any of the currently
present *.md files (ignoring thirdparty).

It is useful not only for possible future tooling that would check the
markdown files syntax, but also as a configuration for editor plugins,
e.g. linter-markdown for atom-linter.

Refs: #7637
Refs: #7727
Refs: #7757
PR-URL: #7729
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Robert Jefe Lindstaedt <[email protected]>
@cjihrig cjihrig mentioned this pull request Aug 11, 2016
@Fishrock123
Copy link
Contributor

does not backport cleanly

MylesBorins pushed a commit that referenced this pull request Sep 9, 2016
Specifies the configuration for remark-lint, a markdown linter.

This configuration does not cause any warnings on any of the currently
present *.md files (ignoring thirdparty).

It is useful not only for possible future tooling that would check the
markdown files syntax, but also as a configuration for editor plugins,
e.g. linter-markdown for atom-linter.

Refs: #7637
Refs: #7727
Refs: #7757
PR-URL: #7729
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Robert Jefe Lindstaedt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Sep 28, 2016
Specifies the configuration for remark-lint, a markdown linter.

This configuration does not cause any warnings on any of the currently
present *.md files (ignoring thirdparty).

It is useful not only for possible future tooling that would check the
markdown files syntax, but also as a configuration for editor plugins,
e.g. linter-markdown for atom-linter.

Refs: #7637
Refs: #7727
Refs: #7757
PR-URL: #7729
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Robert Jefe Lindstaedt <[email protected]>
rvagg pushed a commit that referenced this pull request Oct 18, 2016
Specifies the configuration for remark-lint, a markdown linter.

This configuration does not cause any warnings on any of the currently
present *.md files (ignoring thirdparty).

It is useful not only for possible future tooling that would check the
markdown files syntax, but also as a configuration for editor plugins,
e.g. linter-markdown for atom-linter.

Refs: #7637
Refs: #7727
Refs: #7757
PR-URL: #7729
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Robert Jefe Lindstaedt <[email protected]>
MylesBorins pushed a commit that referenced this pull request Oct 26, 2016
Specifies the configuration for remark-lint, a markdown linter.

This configuration does not cause any warnings on any of the currently
present *.md files (ignoring thirdparty).

It is useful not only for possible future tooling that would check the
markdown files syntax, but also as a configuration for editor plugins,
e.g. linter-markdown for atom-linter.

Refs: #7637
Refs: #7727
Refs: #7757
PR-URL: #7729
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Robert Jefe Lindstaedt <[email protected]>
@gibfahn gibfahn mentioned this pull request Jun 15, 2017
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants