Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Bihlmeyer <e9426626@student.tuwien.ac.at>
Cc: ding@ifi.uio.no
Subject: Re: Preformatting features of Emacs
Date: Mon, 3 Mar 1997 10:31:12 +0100	[thread overview]
Message-ID: <9703030931.AA43512@stud2.tuwien.ac.at> (raw)
In-Reply-To: Steinar Bang's message of 28 Feb 1997 15:12:04 +0100

Hi,

>>>>> On 28 Feb 1997 15:12:04 +0100
>>>>> Steinar Bang <sb@metis.no> said:

 Steinar> Hm... when you're at it,... will it be possible to handle
 Steinar> "other-peoples-quoted-text-broken-by-netscape"? Ie. the
 Steinar> results of long quoted lines hitting Netscape's
 Steinar> break-at-72-chars-when-sending, something like this:

 >>> afsdf adsdsfdasf asdf asdfadsf asdfasdf adsf adsf addfasf
 Steinar> fasdfad
 >>> sfdasdfa dasfadsf fdsfafd afdf
 Steinar> fadsfa
 >> asdfadsfadfadsf dfsadsf dsf asdfadfkjf;kljf;kjhf asfajhjh
 Steinar> fdshkashjd
 >> dsfhaksdfhakf

This is impossible, since "fasdfad" could as well be a comment to the
quoted text, rather than part of it.

Yea, Gnus could analyze the quoted text grammatically, ... But then it
could as well write the reply itself. Not to be expected before Aleph
Gnus, though.

The best thing, IMHO, would be to pop up the question "Encountered
broken quoting-style, report to <bug@netscape.com> ?" if such lines
are found and X-Newsreader has the right value (Mozilla something).

	Robbe


  reply	other threads:[~1997-03-03  9:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-28 10:35 Hrvoje Niksic
1997-02-28 11:32 ` Per Abrahamsen
1997-02-28 14:12   ` Steinar Bang
1997-03-03  9:31     ` Robert Bihlmeyer [this message]
1997-02-28 16:31   ` Hrvoje Niksic
1997-02-28 15:37 ` David Blacka
1997-03-03 11:51   ` Lars Balker Rasmussen
1997-02-28 20:37 ` Paul Franklin
1997-02-28 22:17   ` Hrvoje Niksic
1997-02-28 23:26     ` Stainless Steel Rat
1997-02-28 23:58       ` Jason L Tibbitts III
1997-03-01  0:57         ` Sudish Joseph
1997-03-01  2:05           ` Alan Shutko
1997-03-01  2:53             ` Paul Franklin
1997-03-01 21:45               ` Jason L Tibbitts III
1997-03-01 23:15                 ` C. R. Oldham
1997-03-02 23:24                   ` Alan Shutko
1997-03-01  3:02         ` filladapt.el Stainless Steel Rat
1997-03-05 15:58           ` Disabling scoring for a group C. R. Oldham
1997-03-05 17:15             ` Hrvoje Niksic
1997-03-05 19:08               ` C. R. Oldham
1997-03-06 13:41                 ` Per Abrahamsen
1997-03-07  7:48                   ` Wes Hardaker
1997-03-07 12:41                     ` Per Abrahamsen
1997-03-01  5:52       ` Preformatting features of Emacs Hrvoje Niksic
1997-03-01  0:29     ` Sudish Joseph
1997-02-28 22:22   ` Sudish Joseph
1997-02-28 22:47     ` Per Abrahamsen
1997-02-28 23:56       ` Sudish Joseph
1997-03-01  0:21         ` Stephen Peters
1997-02-28 23:59       ` Sudish Joseph
1997-03-01  1:04         ` Lars Magne Ingebrigtsen
1997-03-01  1:53           ` Sudish Joseph
1997-03-01  2:13           ` Sudish Joseph
1997-03-01  2:17           ` Steven L Baur
1997-03-01  3:06             ` 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=9703030931.AA43512@stud2.tuwien.ac.at \
    --to=e9426626@student.tuwien.ac.at \
    --cc=ding@ifi.uio.no \
    /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).