From: Harry Putnam <reader@newsguy.com>
Subject: Re: Remove jive trailers from messages
Date: 12 Jun 2000 03:27:52 -0700 [thread overview]
Message-ID: <m24s6zmbx3.fsf@reader.ptw.com> (raw)
In-Reply-To: <vxkd7lnehjs.fsf@mesquite.charcoal.com>
Karl Kleinpaste <karl@charcoal.com> writes:
> This is really vile, but what I'm using these days is this group
> property for onelist/egroups lists:
>
> (banner . "^\\(> ?\\)?------------------------------------------------------------------------\n\\(.\\|\n\\)*")
>
> Beware, quoted banners can begin the cutoff, which is (only very
> occasionally) a false positive. Diddle with the "> " stuff to stop
> that particular misfeasance. Personally, I like it that way, because
> people who are dim-witted enough to quote banners are generally people
> who are dim-witted enough to be uninteresting to read at all anyway.
Seems like your RE should have caught this dodo's quoted banner
[...]
> > ------------------------------------------------------------------------
> > Want to win airfare to Vegas for you and 20 friends, $15,000 and a
[...]
But it slips through. Unless I'm reading your RE wrong it says
something like:
Lines begining with >SPC one or no repeat of <spc> one or no repeat of
whole string from >
Neither of the RE below nails it either
(banner . "^\\(> ?\\|>\\)?------------------------------------------------------------------------\n\\(.\\|\n\\)*")
(banner . "^\\(> >\\|?\\)?------------------------------------------------------------------------\n\\(.\\|\n\\)*"))
I notice quite a hefty pause while gnus scans the banner I guess,
then it pops into view.
This was a rare instance to be sure so it is not really a problem,
just made me wonder what I don't know about the "?" operator.
next prev parent reply other threads:[~2000-06-12 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-12 1:51 Harry Putnam
2000-06-12 2:53 ` Karl Kleinpaste
2000-06-12 10:27 ` Harry Putnam [this message]
2000-06-12 20:43 ` Kai Großjohann
2000-06-12 2:54 ` Karl Kleinpaste
2000-06-12 17:05 ` Toby Speight
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=m24s6zmbx3.fsf@reader.ptw.com \
--to=reader@newsguy.com \
/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).