How do you search markdown files with the 72 column limit?

[DanKaplanSES]

The linter requires 72 column lines in markdown files. Compare the "preview" button to the "code" button in this link to see what I mean.

If I want to contribute to the documentation, usually I have to find the part I want to contribute to first. But because the linebreaks in the markdown files don't necessarily relate to the paragraphs, it's difficult to use the Find command on a phrase unless you get lucky and it happens to be on one line in the .md file.

How does one search the documentation source given this limitation? Given enough time, the amount of "false negatives" from searches will add up.

[aduh95]

It's actually 80 characters, and it's being bumped to 120. Like with the HTML version, you can follow links (if your text editor supports them) to arrive to the right section and find the text you're looking for. Otherwise searching for section title is a good bet as they typically don't contain line breaks.

[DanKaplanSES]

Okay thank you that is a helpful tip!

I understand why it's important to have a character limit in code, but what benefit does it provide for markdown files?

[aduh95]

The same benefits as with code I’d say. On the top of my head: no 2D scrolling, comprehensive diffs, git blame is more useful.

[DanKaplanSES]

You meant horizontal scrolling, right? Thanks for the explanation. That makes sense to me.

Is there a way to mark your reply as an answer?