Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: article displaing weirdness
Date: Fri, 29 Jun 2001 20:53:03 +0200	[thread overview]
Message-ID: <iluofr7nmnk.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <eyhewzbelj.fsf@video.uic.vsu.ru> (vvv@vsu.ru's message of "Fri, 29 Jun 2001 17:27:52 +0400")

vvv@vsu.ru writes:

> This article, being displayed in the current version of gnus, looks
> really weird.

In what way?  Your article looked alright to me.  Perhaps a screenshot
is useful.

> i'm seeing a lot of such weirdly-formatted artickes with the current
> version of gnus. perhaps this particular weirdness is caused by
> format=flowed; i've seen a lot of other messages, mostly multipart,
> with similarly weird look.

Does evaluating

(require 'flow-fill)
(defun fill-flowed ())

make any difference?



      reply	other threads:[~2001-06-29 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29 13:27 vvv
2001-06-29 18:53 ` Simon Josefsson [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=iluofr7nmnk.fsf@barbar.josefsson.org \
    --to=jas@extundo.com \
    --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).