headers
Peter S Galbraith | 4 Jan 2004 02:56
Favicon

Re: Bug#225523: mh-index: support for multiple glimpse indices

Hey guys (and Alexander),

Here's a wishlist item from a Debian user.

I've never used multiple search indices with swish++, and we no longer
support glimpse, but I guess using multiple index files would be
applicable to all indexers, right?

Any opinion about this?

Peter
--

-- 
Peter S. Galbraith, MH-E developer  <p.galbraith <at> globetrotter.net>
GPG key 1024/D2A913A1 - 97CE 866F F579 96EE  6E68 8170 35FF 799E
6623'rd GNU/Linux user at the Counter - http://counter.li.org/

Alexander Zangerl <az <at> debian.org> wrote:

> Package: mh-e
> Version: 7.4.3-1
> Severity: wishlist
> 
> the glimpse search support in mh-index is nice, but could be very much
> better if it supported multiple glimpse indices (like exmh supports/suggests).
> 
> i've made a replacement mh-glimpse-execute-search (attached) which does 
> look for indices not just in a single .glimpse directory but in all subdirs of that dir.
> 
> integration of that extra functionality should be quite simple, but upstream
> should be made aware (any likely decide how to do that exactly)
(Continue reading)

Permalink | Reply | 5 comments |
headers
Bill Wohler | 6 Jan 2004 01:31
Picon
Picon
Gravatar

Re: Bug#225523: mh-index: support for multiple glimpse indices

Peter S Galbraith <p.galbraith <at> globetrotter.net> wrote:

> I've never used multiple search indices with swish++, and we no longer
> support glimpse, but I guess using multiple index files would be
> applicable to all indexers, right?
> 
> Any opinion about this?

Of course ;-).

I have one index file for my "current" folders and Real Soon Now will be
creating a second index file for my (tarred and compressed) archived
mail. So yes, an MH-E feature that uses this second index file will be
useful for me too.

A twist in my requirement is that the content files will no longer exist.

Please feel free to submit an MH-E feature request. I'd suggest
including the URL to the Debian bug report too.

p.s. Careful: The M-F-T field in Peter's original message only went to
mh-devel.

--

-- 
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
Permalink | Reply | 4 comments |
headers
Peter S Galbraith | 6 Jan 2004 15:24
Picon
Favicon
Gravatar

Re: Bug#225523: mh-index: support for multiple glimpse indices

Bill Wohler <wohler <at> newt.com> wrote:

> Peter S Galbraith <p.galbraith <at> globetrotter.net> wrote:
> 
> > I've never used multiple search indices with swish++, and we no longer
> > support glimpse, but I guess using multiple index files would be
> > applicable to all indexers, right?
> > 
> > Any opinion about this?
> 
> Of course ;-).
> 
> I have one index file for my "current" folders and Real Soon Now will be
> creating a second index file for my (tarred and compressed) archived
> mail. So yes, an MH-E feature that uses this second index file will be
> useful for me too.

That's a good point.
I could do that too instead of wasting cycles every night.

> A twist in my requirement is that the content files will no longer exist.

Content files?

> Please feel free to submit an MH-E feature request. I'd suggest
> including the URL to the Debian bug report too.

Will do.

> p.s. Careful: The M-F-T field in Peter's original message only went to
(Continue reading)

Permalink | Reply | 1 comment |
headers
Satyaki Das | 7 Jan 2004 03:53
Picon

Re: Bug#225523: mh-index: support for multiple glimpse indices

Bill Wohler <wohler <at> newt.com> wrote:

> Peter S Galbraith <p.galbraith <at> globetrotter.net> wrote:
> 
> > Any opinion about this?

A good idea.

> I have one index file for my "current" folders and Real Soon Now will be
> creating a second index file for my (tarred and compressed) archived
> mail. So yes, an MH-E feature that uses this second index file will be
> useful for me too.
> 
> A twist in my requirement is that the content files will no longer exist.

Recently while installing dictd (a dictionary server) on my
home machine, I came across dictzip which is compatible to
gzip.  It has extra header info, that allows it to do "random"
access into the stored data (so you wouldn't have to
uncompress the whole dictionary to find the meaning of
TANSTAAFL).

You should probably be using something like that to archive
your mail.  Then when you want to populate an index folder you
would only expand out the necessary segments.  Wouldn't that
be cool.

Satyaki

PS: Since this doesn't have much to say about the current bug,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jeffrey C Honig | 7 Jan 2004 04:19
Face

Re: Bug#225523: mh-index: support for multiple glimpse indices

Satyaki Das <satyaki <at> chicory.Stanford.EDU> wrote:

> Recently while installing dictd (a dictionary server) on my
> home machine, I came across dictzip which is compatible to
> gzip.  It has extra header info, that allows it to do "random"
> access into the stored data (so you wouldn't have to
> uncompress the whole dictionary to find the meaning of
> TANSTAAFL).

Cool, sounds like a good backend for mh-mailutils!

      ;-)

Thanks.

Jeff

--

-- 
Jeffrey C. Honig <jch <at> honig.net>
http://www.honig.net/jch
GnuPG ID:14E29E13 <http://www.honig.net/jch/key.shtml>
Permalink | Reply | 0 comments |
headers
Bill Wohler | 7 Jan 2004 19:23
Picon
Picon
Gravatar

Re: Bug#225523: mh-index: support for multiple glimpse indices

Peter S Galbraith <psg <at> debian.org> wrote:

> Bill Wohler <wohler <at> newt.com> wrote:
> 
> > I have one index file for my "current" folders and Real Soon Now will be
> > creating a second index file for my (tarred and compressed) archived
> > mail. So yes, an MH-E feature that uses this second index file will be
> > useful for me too.
> 
> That's a good point.
> I could do that too instead of wasting cycles every night.
> 
> > A twist in my requirement is that the content files will no longer exist.
> 
> Content files?

Here's a more specific description. I've got a folder called +archive.
Several months into the new year, I create a directory for the past
year. For example, later I'll create +archive/2003 and use pick and
refile to rebuild my folder hierarchy under +archive/2003 (e.g.
+archive/2003/a/peter.galbraith and +archive/2003/lists/mh-e) with
messages from 2003. This is what I meant by content files. I'll then
append the swish index for 2003 into the existing swish index in
+archive, tar up the 2003 directory into 2003.tgz, and delete the 2003
directory (content files).

With MH, The compressed tarball saves LOTS of inodes and space.

Satyaki is on target with dictzip. I'll have to have a look to see how
it handles tar archives.
(Continue reading)

Permalink | Reply | 0 comments |
headers
wohler | 13 Jan 2004 02:15
Picon

htdocs/manual index.html,1.3,1.4

Update of /cvsroot/mh-e/htdocs/manual
In directory sc8-pr-cvs1:/tmp/cvs-serv11853/manual

Modified Files:
	index.html 
Log Message:
Mention that one can use "M-x customize-group RET mh RET" to see what
customization variables are available.

Index: index.html
===================================================================
RCS file: /cvsroot/mh-e/htdocs/manual/index.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- index.html	12 Dec 2003 22:15:57 -0000	1.3
+++ index.html	13 Jan 2004 01:15:45 -0000	1.4
 <at>  <at>  -140,9 +140,9  <at>  <at> 

 <p>MH-E has changed much since the <a
 href="http://www.ics.uci.edu/~mh/book/mh-e/">old MH-E manual</a> was
-written. Most the commands and customizations in the manual are
-obsolete, but the gist of the program is the same. However, the
-tutorial is still applicable.
+written for version 5.0.2. Most the commands and customizations in the
+manual are obsolete, but the gist of the program is the same. However,
+the tutorial is still applicable.

 <p>An manual update is in the works and will appear when version
 8.0 of MH-E is released, which will be roughly in spring of 2004.
(Continue reading)

Permalink | Reply | 0 comments |
headers
wohler | 13 Jan 2004 02:15
Picon

htdocs ChangeLog,1.55,1.56

Update of /cvsroot/mh-e/htdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv11853

Modified Files:
	ChangeLog 
Log Message:
Mention that one can use "M-x customize-group RET mh RET" to see what
customization variables are available.

Index: ChangeLog
===================================================================
RCS file: /cvsroot/mh-e/htdocs/ChangeLog,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -d -r1.55 -r1.56
--- ChangeLog	12 Dec 2003 22:15:57 -0000	1.55
+++ ChangeLog	13 Jan 2004 01:15:45 -0000	1.56
 <at>  <at>  -1,3 +1,8  <at>  <at> 
+2004-01-12  Bill Wohler  <wohler <at> newt.com>
+
+	* manual/index.html: Mention that one can use "M-x customize-group
+	RET mh RET" to see what customization variables are available.
+
 2003-12-12  Bill Wohler  <wohler <at> newt.com>

 	* index.php, template, devel/index.php, manual/index.html,
Permalink | Reply | 0 comments |
headers
SourceForge.net | 14 Jan 2004 03:46
Picon
Favicon

[ mh-e-Patches-876569 ] Unix mbox From line in mh-spamassassin-whitelist

Patches item #876569, was opened at 2004-01-13 21:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=313357&aid=876569&group_id=13357

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jym Dyer (jym_dyer)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unix mbox From line in mh-spamassassin-whitelist

Initial Comment:
The mh-spamassassin-whitelist invokes spamassassin with
the "--remove-markup" option, then replaces the message
with the results.  Unfortunately, this prepends the
message with a Unix mbox "From line".  The
"--noadd-from" option is also needed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=313357&aid=876569&group_id=13357
Permalink | Reply | 0 comments |
headers
SourceForge.net | 14 Jan 2004 19:29
Picon
Favicon

[ mh-e-Patches-876569 ] Unix mbox From line in mh-spamassassin-whitelist

Patches item #876569, was opened at 2004-01-13 18:46
Message generated for change (Comment added) made by wohler
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=313357&aid=876569&group_id=13357

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jym Dyer (jym_dyer)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unix mbox From line in mh-spamassassin-whitelist

Initial Comment:
The mh-spamassassin-whitelist invokes spamassassin with
the "--remove-markup" option, then replaces the message
with the results.  Unfortunately, this prepends the
message with a Unix mbox "From line".  The
"--noadd-from" option is also needed.

----------------------------------------------------------------------

>Comment By: Bill Wohler (wohler)
Date: 2004-01-14 10:29

Message:
Logged In: YES 
user_id=93690
(Continue reading)

Permalink | Reply | 0 comments |

Gmane