[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug-mailutils] Re: Buglets in Mailutils MH
From: |
Sergey Poznyakoff |
Subject: |
[bug-mailutils] Re: Buglets in Mailutils MH |
Date: |
Tue, 19 Aug 2003 12:10:38 +0300 |
> 0) As I said in another message, the components file wasn't copied to
> the etcdir in `make install'. Neither was a replgroupcomps file
> which you don't seem to have.
Yes, it will be fixed.
> 1) If I leave the cc: line empty, nmh will strip it in the out-going
> message, since it wasn't used. It's still listed in this message by
> mh-mu.
Hmm, is that critical?
> 2) MH-E scans the last 200 messages by default. This doesn't work in
> mu-mh:
I'm going to fix it today.
> 3) Do you have a timeline on implementing `ali'? It's it going to be a
> while then we should implement a by-pass in MH-E when mu-mh is used.
Yes, I'll add it to the repository by the end of this week.
> FYI, The only bits of your patch that were still relevant after my
> initilization code overhaul were for scan error in mh-e.el (applied) and
> for pick in mh-pick.el. I haven't done pick yet. I need to understand
> the single dash stuff that you added first
Do you mean the changes to mh-pick-regexp-builder? These add
the command line options necessary to search for arbitrary
components. All implementations of pick have special options
-cc, -date, -from and -subject that allow to search for corresponding
components. Any other component is searched using option --COMPNAME,
for example: `pich --x-mailer mh-e'. Mailutils `pick' supports this
option using a certain kludge that I've described in one of my
previous postings, but it prefers the following syntax for this
purpose: `--component=COMPNAME --pattern=PATTERN'.
So, the changes in question allow you to specify any component in the
search-pattern buffer (along with the default five components it
presents). Then this component is searched using a command line syntax
proper for the current implementation of MH.
Regards,
Sergey