Gnus development mailing list
 help / color / mirror / Atom feed
From: Ralf Angeli <dev.null@iwi.uni-sb.de>
Subject: Re: [flow-fill.el] Filling of quoted blank lines
Date: Thu, 04 Dec 2003 11:09:03 +0100	[thread overview]
Message-ID: <bqn14b$l62$1@quimby.gnus.org> (raw)
In-Reply-To: <ilu4qwha3od.fsf@latte.josefsson.org>

* Simon Josefsson (2003-12-04) writes:

> I hope this is slightly more robust, please test it.

Hm, doesn't seem to work correctly.

I am testing it with an article in de.comp.text.tex (MID:
<news:3fcaafbd$0$22267$9b622d9e@news.freenet.de>) which encloses the
following lines:

,----
| >> unterscheidet einen "Heinrich Paul Mueller (H.P.Mueller)" vom
| >> "Hans-Peter Mueller (H.-P. Mueller").
| > 
| > Wenn das in der neuesten verfügbaren Version so ist, wäre wohl ein
| > Bug-Report an den Autor des custom-bib-Pakets angebracht.
`----

If I understand correctly, your code will first search forward until
it finds ` $'.  In the above example point will then be at the end of
the "empty" line.  Then (forward-char 1) is called and point will be
at the beginning of `> Wenn das ...'.  So the following test regarding
`skiponeline' will never see the the "empty" line.

There is another article on Gmane I am using for testing.  You can
find it at
<URL:http://article.gmane.org/gmane.linux.debian.ports.powerpc/14615>.

With the new code e.g. the line starting with "... Seriously, folks,
..." in the second paragraph will get filled with the first paragraph.
I haven't looked into it and cannot tell, where the problem is though.

> It also fixes a long-standing problem in that:
>
> foo
> -- 
> bar
>
> would be flowed together, when it shouldn't.

Yes, I saw this as well and it is good that you address it with the
new code because the solution I proposed was even more error prone as
a line ending with `some text> ' is more common than a dash at the
end.

> There really need to be a regression test harness for flow-fill, it is
> difficult to tell what consequences even a minor change would have.

If you want to, I could post some test articles to this thread,
e.g. like the two mentioned above.  I just have to figure out how I
can add `format=flowed' to the header and what test cases would be
needed exactly.

Regards,
Ralf

-- 
 Moo!
     `~~_.
______',,/______ No gnus is bad news.



  reply	other threads:[~2003-12-04 10:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 17:35 Ralf Angeli
2003-12-02 18:00 ` Simon Josefsson
2003-12-02 18:16   ` Ralf Angeli
2003-12-03  8:23   ` Ralf Angeli
2003-12-03 22:07     ` Ralf Angeli
2003-12-03 23:21       ` Simon Josefsson
2003-12-04 10:09         ` Ralf Angeli [this message]
2003-12-04 15:36           ` Simon Josefsson
2004-01-19 10:05 ` Ralf Angeli
2004-01-27 14:43   ` Ralf Angeli
2004-01-27 20:46     ` Simon Josefsson
2004-01-28  8:04       ` Ralf Angeli
2004-01-28 16:47         ` Simon Josefsson

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='bqn14b$l62$1@quimby.gnus.org' \
    --to=dev.null@iwi.uni-sb.de \
    --cc=angeli@iwi.uni-sb.de \
    /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).