Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: ding@gnus.org
Subject: Re: disable "You have lines longer than 79 characters.  Really post? (y or n) y"
Date: Mon, 27 May 2019 22:53:53 +0200	[thread overview]
Message-ID: <86imtvd3fi.fsf@zoho.eu> (raw)
In-Reply-To: <87k1eie7su.fsf@x230.onfire.org>

Christian Barthel wrote:

>> 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.

HTML-formatted messages I don't like, but you
can get away with them like this - I think!
I don't remember what exactly do what
anymore :$

;;; HTML and NON-ASCII
(setq gnus-inhibit-images t)
(setq gnus-inhibit-mime-unbuttonizing nil)
(setq mm-discouraged-alternatives '("text/html" "text/richtext"))
(setq mm-text-html-renderer 'w3m)

The second-last line and the last seems to
contradict each other... :)

As for the line length, I think that is some
relic from time passed. I might be wrong tho?

Anyway when I see a mail with to long lines to
the point that it disturbs me, I do
`gnus-article-fill-cited-article'. This ruins
pretty code and ASCII art, so sometimes I have
to go back and forth. For plain text tho it
works well in my experience.

Just some random thoughts :)

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal




      reply	other threads:[~2019-05-27 20:53 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
2019-05-27 20:53           ` Emanuel Berg [this message]

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=86imtvd3fi.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --cc=ding@gnus.org \
    /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).