Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Writing one sentence per line

sive.rs

Post reply on HN
Print view View original

101–110 of 307 posts

Re: Writing one sentence per line

#101

Post by exysle »

Disruptive_Dave wrote: post #8

This sentence has five words. Here are five more words. Five-word sentences are fine. But several together become monotonous. Listen to what is happening. The writing is getting boring. The sound of it drones. It’s like a stuck record. The ear demands some variety. Now listen. I vary the sentence length, and I create music. Music. The writing sings. It has a pleasant rhythm, a lilt, a harmony. I use short sentences.…

He is not saying short sentences are necessary, he is saying that each sentence stands out with a newline, which means they can be judged at an individual level.

Re: Writing one sentence per line

#102

Post by xigoi »

capableweb wrote: post #61
wheybags wrote: post #53

Slightly off topic, but a pet peeve of mine is how you don't get a real line break in markdown when you insert a newline. Sometime I want a line break without a vertical apace for a new paragraph, I can't be the only one here! I know I can normally just add a br tag, but that looks nasty when you read it as plain text.

That depends on the markdown implementation (like so many features). But most of them implement "two trailing spaces on previous line force line-break" so you can (in most places) do something like this: This is a paragraph with no linebreaks. This is a paragraph with one linebreak but without trailing spaces This is a paragraph with one line break and trailing spaces on previous line That will render correctly on Gi…

Significant trailing whitespace is awful. Many editors have it invisible and/or automatically remove it.

Re: Writing one sentence per line

#103

Post by eCa »

drewg123 wrote: post #90

Just please, for the love of god, don't do it in slack. Nothing annoys me more than a colleague writing a long slack message when I'm AFK, and having my watch buzz like an angry bee when they hit one carriage return (and send a new slack message) every 10 seconds.

Personally, I have mapped ’send’ to cmd+enter, to avoid accidentally sending too soon. Also, to make it behave similarly within a code block as without.

Re: Writing one sentence per line

#104

Post by secondcoming »

drewg123 wrote: post #90

Just please, for the love of god, don't do it in slack. Nothing annoys me more than a colleague writing a long slack message when I'm AFK, and having my watch buzz like an angry bee when they hit one carriage return (and send a new slack message) every 10 seconds.

Joke's on you for connecting your watch to Slack.

Re: Writing one sentence per line

#105

Post by drewg123 »

Beltalowda wrote: post #95
drewg123 wrote: post #90

Just please, for the love of god, don't do it in slack. Nothing annoys me more than a colleague writing a long slack message when I'm AFK, and having my watch buzz like an angry bee when they hit one carriage return (and send a new slack message) every 10 seconds.

You should really be angry at Slack and not your colleagues. There are loads of ways to prevent this like sending at most one alert per user per minute (if message is unread). It's not rocket science. Most times when loads of people are "doing it wrong" then it's the technology that is at fault, and not the people.

Yes, I'm angry at slack. No other messaging system I've used does this..

Re: Writing one sentence per line

#108

Post by TheFreim »

BeFlatXIII wrote: post #93
kadoban wrote: post #84

Earlier quoted context omitted.

That's about as unnatural for most people as newline per sentence, and has the added risk that you'll accidentally publish like that and it'll look weird. One per line would be _much_ harder to accidentally publish because it's more obvious.

Two spaces between sentences is how I've always typed them, even if it's in HTML or MD or other forms that will condense them into a single space in the final render. The two spaces mark a clear intent to end a sentence instead of a period to punctuate an abbreviation.

Many people learned to add two spaces to the end of each sentence which is now built in to their muscle memory. My father learned to type adding two spaces to the end of every sentence, they tried to teach that to me in computer class in middle school but since I had a lot of experience typing already without it I never felt motivated to change my habit to add two spaces. I never really saw the point, in most formats I can't see the two spaces.

Re: Writing one sentence per line

#109

Post by [deleted] »

m4lvin wrote: post #49
ketzu wrote: post #7

Earlier quoted context omitted.

> diffs make way more sense when there is only one sentence per line I did the same thing for some time for papers at university for the same reason. It used to annoy me, because I hate to change for my tools, I rather have my tools support my workflow: There should be a nicer diff for that.

git diff --word-diff

[deleted]

Re: Writing one sentence per line

#110

Post by drewg123 »

secondcoming wrote: post #104
drewg123 wrote: post #90

Just please, for the love of god, don't do it in slack. Nothing annoys me more than a colleague writing a long slack message when I'm AFK, and having my watch buzz like an angry bee when they hit one carriage return (and send a new slack message) every 10 seconds.

Joke's on you for connecting your watch to Slack.

Sadly, I have no choice. I have a Garmin connected to an iPhone. Even when I disable most notifications for an app, it will still hit my watch.

On Android, I could filter out which apps could notify the watch, on ios, it seems Garmin has not been able to do that.

Post reply on HN