Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
at first sight I thought you were mad at this unhelpful syntax (mis)feature XD ...
of course it's a feature, but I have misused markdown ever so often BUT of course one should check how the content looks when it gets rendered before doing a final commit -
Proper editors have a word break. Also, I have seen renderers that don't insert a new paragraph, but accept the line end, in particular in enumerations.
-
Long lines are fine, if they make for a paragraph with helpful information (as @Fast-Nop said, any proper editors have word wrap to break long lines accomodating one width).
Single linebreak in Markdown is just useless on top level, yeah. They should learn the ways of Markdown. -
hitko31483yNo, fuck you for not using word wrap. No one wants to read through 10 lines of changes when someone adds a word to the paragraph and suddenly all lines shift.
(top: 120 char lines, bottom: a single line) -
@hitko Sorry I'm already taken by @rutee07
But alr8 you guys have a point, I just got mad when the PR was 300 chars wide -
I don't get why people argue in favor of long lines. Have you ever tried resolving a merge conflict where everthing is on one line. That shit grinds my gears!
I say one line should never contain more than one sentence in markdown or LaTeX for that matter.
How many times do I need to tell you, markdown does not convert a single linebreak to a new paragraph.
STOP WRITING LINES THAT ARE MORE THAN 300 CHARACTERS LONG IN A MARKDOWN FILE HOW THE FUCK AM I SUPPOSED TO REVIEW THAT.
rant