Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@pdc.kth.se>
Subject: Re: Problems with flow-filled
Date: 21 Apr 2000 13:16:46 +0200	[thread overview]
Message-ID: <ilur9bzsnz5.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Graham Murray's message of "21 Apr 2000 07:29:35 +0000"

Graham Murray <graham@barnowl.demon.co.uk> writes:

> 1) On entering a message using flow-filled, *no* headers are
>    displayed. Pressing 't' displays the normal header set. Pressing
>    't' again displays the full header set. A third time it displays
>    the normal header set.
> 
> 2) The text is not be "flowed" correctly. At the end of a line (and in
>    the middle of a word) I see a '?' and the text continues on the
>    next line.
> 
> This is using the CVS as of 6:45 GMT today.

Could you place the mail (if possible) on the web somewhere so we can
take a look?



      reply	other threads:[~2000-04-21 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-21  7:29 Graham Murray
2000-04-21 11:16 ` 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=ilur9bzsnz5.fsf@badis.pdc.kth.se \
    --to=jas@pdc.kth.se \
    /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).