public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Martin McCormick <martin@dc.cis.okstate.edu>
To: blinux-list@redhat.com
Subject: A Filter to Speed up nmh Message Scans
Date: Mon, 27 May 2002 12:01:55 -0500	[thread overview]
Message-ID: <200205271701.g4RH1to71968@dc.cis.okstate.edu> (raw)

	I just wrote a little C program that I use on large
message folders to speed up the process of scanning large numbers
of messages.  You have to set up a format file to only pass the
message number plus the subject.  My filter ignores the message
number because it always changes, but if there are more than two
messages with the same subject, you only hear the first scan.
It silently skips all the rest of the lines with the same subject
and then wakes up when the subject changes.

	I have everything you need to make it run in a uuencoded
file that decodes to form a file called subjects.tar.gz.  When
you uudecode it, it unpacks to a directory called subjects.  In
there is a file called doc.txt and the source called subjects.c .

	I tell you how to build it and what its limitations are .

	The main thing that throws it off is when several people
post subjects that are essentially the same subject, but have
been re-spelled or otherwise reworked.  My filter does a few
tricks to get around common variations, but it is not
sophisticated at all.  All I do is to force all words in the
subject to upper case, remove all whitespace and punctuations.
That still isn't enough, but anything else gets in to the realm
of very complex.  This is quick and dirty.

	The uuencoded file is 60 lines long and I could post it
to the list, but that's not fair to those who don't care.

Martin McCormick WB5AGZ  Stillwater, OK 
OSU Center for Computing and Information Services Network Operations Group




                 reply	other threads:[~ UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200205271701.g4RH1to71968@dc.cis.okstate.edu \
    --to=martin@dc.cis.okstate.edu \
    --cc=blinux-list@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).