Hacker News new | past | comments | ask | show | jobs | submit login

The author writes,

“my plain text emails, written with glorious 80 column limit, would be viewed with random line breaks on mobile clients”

He’s doing it wrong. You should write your emails with a 998 character limit. Only add linebreaks between paragraphs. If your paragraph is going longer than 998 characters, recast. This way, the client will break the lines properly and the reader won’t have to read a chaotic mess of random linebreaks. Your email will look good on phones and everywhere else.




I'm a fellow mutt user - I've always used ~80 column limit... it makes me wince thinking of removing it!

I do hear from non-nerd contacts asking about the line breaks, perhaps you're right, maybe it's time!


I used to do the same. Sometimes I would remember to squash my convenience linebreaks back down into real paragraphs for the recipient.

I assume you use vim or emacs for editing -- vertical movement between lines is more convenient than movement within a single wrapped line.

In vim, you can use gj or gk for vertical movement within a wrapped line.

At some point I decided to make the arrow keys more useful:

  map <silent> <Up> gk
  map <silent> <Down> gj


Try it. You’ll never go back.


Why 998?


It's part of the email specification. Look at https://www.rfc-editor.org/rfc/rfc5322#section-2.1.1.


That spec literally recommends 80 char lines.


> That spec literally recommends 80 char lines.

You mean this recommendation?

> The more conservative 78 character recommendation is to accommodate the many implementations of user interfaces that display these messages which may truncate, or disastrously wrap, the display of more than 78 characters per line, in spite of the fact that such implementations are non-conformant to the intent of this specification (and that of [RFC5321] if they actually cause information to be lost). Again, even though this limitation is put on messages, it is incumbent upon implementations that display messages to handle an arbitrarily large number of characters in a line (certainly at least up to the 998 character limit) for the sake of robustness.

Are there many user interfaces that can't handle more than 78 characters anymore? Even terminal windows wrap now. I'm inclined to believe that the 78 character recommendation really isn't that important anymore.

That said, I'm curious if the 998 restriction really is important too. That comes from here:

> The 998 character limit is due to limitations in many implementations that send, receive, or store IMF messages which simply cannot handle more than 998 characters on a line.

Are there many such implementations hanging around that can't handle more than 998 characters?


I don’t have hard information but I believe so. If you have a line with more than 998 characters you’re taking a risk that your email will be rejected. But I’m pretty sure there is never any problem with lines <= 998 characters, and it works far better on more devices than trying to break lines to fit some imaginary screen, which always ends up in a mess.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: