From: Christian Barthel <bch@online.de>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: ding@gnus.org
Subject: Re: disable "You have lines longer than 79 characters. Really post? (y or n) y"
Date: Wed, 22 May 2019 19:08:17 +0200 [thread overview]
Message-ID: <87k1eie7su.fsf@x230.onfire.org> (raw)
In-Reply-To: <86mujjpu2r.fsf@zoho.eu> (Emanuel Berg's message of "Sat, 18 May 2019 19:10:20 +0200")
Emanuel Berg <moasenwood@zoho.eu> writes:
> OK, but what is the problem to begin with?
Many mailinglists and newsgroups have rules that state that lines
shouldn't be longer than 80 chars or even smaller. The OpenBSD
mailinglist rule for example, looks like [1]:
| Plain text, 72 characters per line
| Many subscribers and developers read their mail on
| text-based mailers like mail(1), emacs or mutt, and they
| often find HTML-formatted messages (or lines that stretch
| beyond 72 characters) unreadable.
The EmacsWiki [2] states something similar and for written
sentences, there is some argumentation why it's a useful line
length.
But I guess whether this applies to URLs is a different matter
(because you don't read urls like a sentence). Anyway, I trust
Gnus and stick with that limit :-)
[1] https://www.openbsd.org/mail.html
[2] https://www.emacswiki.org/emacs/EightyColumnRule
--
Christian Barthel <bch@online.de>
next prev parent reply other threads:[~2019-05-22 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 1:19 Emanuel Berg
2019-05-13 3:12 ` Eric Abrahamsen
2019-05-13 5:31 ` Emanuel Berg
2019-05-13 5:45 ` Emanuel Berg
2019-05-16 6:52 ` Christian Barthel
2019-05-16 16:48 ` Eric Abrahamsen
2019-05-16 18:25 ` Andreas Schwab
2019-05-16 18:33 ` Eric Abrahamsen
2019-05-16 22:36 ` Emanuel Berg
2019-05-16 23:05 ` (where) is ding@gnus.org archived? (was: Re: disable "You have lines longer than 79 characters. Really post? (y or n) y") Emanuel Berg
2019-05-17 1:25 ` disable "You have lines longer than 79 characters. Really post? (y or n) y" Eric Abrahamsen
2019-05-17 2:02 ` Emanuel Berg
2019-05-17 6:33 ` Christian Barthel
2019-05-18 17:10 ` Emanuel Berg
2019-05-22 17:08 ` Christian Barthel [this message]
2019-05-27 20:53 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1eie7su.fsf@x230.onfire.org \
--to=bch@online.de \
--cc=ding@gnus.org \
--cc=moasenwood@zoho.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).