Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: pgnus 0.25 problem
Date: 11 Sep 1998 16:20:46 +0200	[thread overview]
Message-ID: <877lzawx1d.fsf@slowfox.do.uunet.de> (raw)
In-Reply-To: Hrvoje Niksic's message of "11 Sep 1998 15:03:39 +0200"

>>>>> On 11 Sep 1998, Hrvoje Niksic said:

  Hrvoje> Applied to Gnus, this means that it should try to be as lax
  Hrvoje> as possible when parsing the headers (in the above case, it
  Hrvoje> should ignore the semicolon and perhaps assume the charset
  Hrvoje> is latin1), and ignore them when they're totally bogus.

I think completely ignoring them is not the right thing.  Suppose I
get a message which looks bogus when shown by Gnus.  I might then
assume that it really *is* bogus.  But maybe just the headers are
bogus, and with some manual effort, the message itself can be
salvaged.  Therefore I propose that at least a message be output
telling the user that Gnus is (otherwise) ignoring the bogus Frumple
header.

kai
-- 
OOP: object oriented programming;  OOPS: object oriented mistakes


  parent reply	other threads:[~1998-09-11 14:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-11  8:18 Jakub Martyński
1998-09-11  9:13 ` Lars Magne Ingebrigtsen
1998-09-11 13:03   ` Hrvoje Niksic
1998-09-11 14:19     ` Lars Magne Ingebrigtsen
1998-09-11  7:33       ` François Pinard
1998-09-11 15:17       ` Hrvoje Niksic
1998-09-11 14:20     ` Kai Grossjohann [this message]
1998-09-11 15:14       ` Hrvoje Niksic
1998-09-11 20:59         ` Kai Grossjohann
1998-09-12  6:21           ` Lars Magne Ingebrigtsen

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=877lzawx1d.fsf@slowfox.do.uunet.de \
    --to=grossjohann@amaunet.cs.uni-dortmund.de \
    --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).