{"action":"created","issue":{"url":"https://api.github.com/repos/jlevy/the-art-of-command-line/issues/167","labels_url":"https://api.github.com/repos/jlevy/the-art-of-command-line/issues/167/labels{/name}","comments_url":"https://api.github.com/repos/jlevy/the-art-of-command-line/issues/167/comments","events_url":"https://api.github.com/repos/jlevy/the-art-of-command-line/issues/167/events","html_url":"https://github.com/jlevy/the-art-of-command-line/issues/167","id":93981816,"number":167,"title":"Lines are too freaking long!","user":{"login":"poxu","id":2285091,"avatar_url":"https://avatars.githubusercontent.com/u/2285091?v=3","gravatar_id":"","url":"https://api.github.com/users/poxu","html_url":"https://github.com/poxu","followers_url":"https://api.github.com/users/poxu/followers","following_url":"https://api.github.com/users/poxu/following{/other_user}","gists_url":"https://api.github.com/users/poxu/gists{/gist_id}","starred_url":"https://api.github.com/users/poxu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/poxu/subscriptions","organizations_url":"https://api.github.com/users/poxu/orgs","repos_url":"https://api.github.com/users/poxu/repos","events_url":"https://api.github.com/users/poxu/events{/privacy}","received_events_url":"https://api.github.com/users/poxu/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-07-09T07:49:33Z","updated_at":"2015-07-13T05:43:26Z","closed_at":null,"body":"WTF man? The text, which advises you to learn more about vim is formatted in a manner, which makes it hard to edit it with vim! \r\n\r\nOk, maybe you don't use vim, but fixing a typo leads to git thinking a whole paragraph was changed! Reading the diffs without using special viewers is no fun at all!\r\n\r\nIf that was plain text I would understand. You wanted text width to adapt to screen size I would think. But you're using markdown, which removes line breaks before rendering text!\r\n\r\nDid you do it on purpose :) ?\r\n\r\nP. S. I really like your work, but it's not as easy to contribute as it could be. Please, please make line 80 characters long! Or 120 characters long at least."},"comment":{"url":"https://api.github.com/repos/jlevy/the-art-of-command-line/issues/comments/120820387","html_url":"https://github.com/jlevy/the-art-of-command-line/issues/167#issuecomment-120820387","issue_url":"https://api.github.com/repos/jlevy/the-art-of-command-line/issues/167","id":120820387,"user":{"login":"jlevy","id":2058167,"avatar_url":"https://avatars.githubusercontent.com/u/2058167?v=3","gravatar_id":"","url":"https://api.github.com/users/jlevy","html_url":"https://github.com/jlevy","followers_url":"https://api.github.com/users/jlevy/followers","following_url":"https://api.github.com/users/jlevy/following{/other_user}","gists_url":"https://api.github.com/users/jlevy/gists{/gist_id}","starred_url":"https://api.github.com/users/jlevy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jlevy/subscriptions","organizations_url":"https://api.github.com/users/jlevy/orgs","repos_url":"https://api.github.com/users/jlevy/repos","events_url":"https://api.github.com/users/jlevy/events{/privacy}","received_events_url":"https://api.github.com/users/jlevy/received_events","type":"User","site_admin":false},"created_at":"2015-07-13T05:43:25Z","updated_at":"2015-07-13T05:43:25Z","body":"@poxu well, when it comes to religion, it's best to avoid controversy but still do what you think is right. ;)\r\n\r\n@olivertaylor Thanks for the links. I've done this before, but hadn't seen the term \"semantic linefeeds.\" It's helpful to give it a name, yes, as I think many-author Markdown documents are becoming increasingly common on Github. Of course even this seemingly sensible suggestion is evidently [rife with controversy](https://news.ycombinator.com/item?id=4642395), but some of that is particular to MediaWiki format, not Markdown.\r\n\r\nIn programming, the modern, probably correct answer to feuds about this stuff is to use automated formatting, e.g. `gofmt`, `yapf`, IntelliJ, etc. Those perl scripts could help but don't actually understand Markdown. Longer term, it might be best to have an automated Markdown formatting tool (fully compatible with Github) run before every commit that does breaks via heuristics, probably mainly on sentences. It would enforce conventions and also migrate nonconforming documents. I might look into writing one, if no one is aware of one?\r\n"}}