Switch from `` code blocks to 4 spaces

[jedahan]

This makes it a lot easier to copy paste with the mouse in the commandline.

I am testing now with a few implementations to make sure it works fine.

[igorshubovych]

Oh, man.
You did so much work without asking ahead. Please tell me that you did some script for it and you did not do it manually.

In cases like this it is better to discuss it in tickets first, before doing any job. This will be most likely rejected, because linter and the most of the clients depends on the backticks when parsing. Usually clients parse the format and present in the nice way.

E.g. NodeJS client present it this way

It is quite easy to do copy-pasting.

[jedahan]

It was a one line script with sed, so not a lot of work. This was kinda the introduction to discuss the change. I would have to change https://github.com/tldr-pages/tldr-lint/blob/master/lib/tldr-parser.js#L736 and https://github.com/tldr-pages/tldr-lint/blob/master/lib/tldr-parser.js#L758 to allow for 8 spaces, etc.

When using a client, they are formatted in an easy way to copy paste, but if you open the markdown files themselves it is a bit tougher. Of course most people should be using a client, but I thought it looks nicer with 8 spaces (and matches the output of most tools that parse it).

Would people be vehemently against changing the tldr-linter to look for 8 spaces instead of backticks?

I feel like it would actually remove some of the client-side work but maybe i'm totally off there...

[jedahan]

nevermind, saw a bunch of implementations, they rely on '`'

[waldyrious]

I would still like this to be discussed. See #686 (comment)

[rubenvereecken]

Poor man actually checked out the generated parser file.

[jedahan]

Well, never worked with any lexer or parser, so didnt even look at the .yy or .l files. Still don't know if these are the right places to change things, but:

https://github.com/tldr-pages/tldr-lint/blob/master/tldr.yy#L53-L55 and https://github.com/tldr-pages/tldr-lint/blob/master/tldr.l#L138-L141 probably relevant.

Somewhat related, maybe generated files shouldn't be checked into the source repo? But I don't see how the generated files are made. Maybe a makefile or just that jison thing?

[rubenvereecken]

I had that problem as well, but I needed the generated files to be present upon npm install. A work around would be to use jison upon tldr-lint startup to generate the needed source code, but that's not a very pretty way to go about it.

Anyway, we'll continue the conversation