Andy Bradford | 1 Oct 2010 07:09

Mh_Init called too soon?

Hello,

I tried override Mh_ReplyAllSetup from mh.tcl by creating:

~/.exmh/lib/mh.patch

and  updating  tclIndex,  however,  because  Mh_Init  is  called  before
SourceHook_Init (in main.tcl), it wasn't loading my patch. Attached is a
patch to main.tcl that seems innocuous. Any reason why this shouldn't be
moved?

Additionally,   maybe   Mh_ReplyAllSetup   should   be   searching   for
replgroupcomps instead of replcomps in mh.tcl? I realize that many users
might already  be accustomed  to the  current behavior  (replcomps being
used for  both Mh_ReplyAllSetup and  Mh_ReplySetup), which is why  I was
trying to put it in my own lib.

Andy
Attachment (main.tcl.patch): application/x-patch, 564 bytes
_______________________________________________
Exmh-workers mailing list
Exmh-workers <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-workers
Andy Bradford | 1 Oct 2010 07:48

Re: Mh_Init called too soon?

Thus said "Andy Bradford" on 30 Sep 2010 23:09:25 MDT:

> Additionally,   maybe  Mh_ReplyAllSetup   should   be  searching   for
> replgroupcomps instead of replcomps in mh.tcl?

Ok,  so I  applied my  own patch  and surprisingly,  it didn't  have any
effect;  or  rather,  my  mh.patch  loaded,  but  *it*  had  no  effect.
Mh_ReplyAllSetup  is  never  called  anywhere! It  looks  like  all  the
Reply vs  ReplyAll is  handled in  msg.tcl. I  do notice,  however, that
if  Msg_Reply  is  called  with  no arguments,  that  it  sets  args  to
Mh_ReplySetup. Are Mh_ReplySetup and Mh_ReplyAllSetup not supposed to be
used anymore?

Andy

Gmane