Re: Exmh releases, and a large bunch of small changes in the exmh tre e...

On Mon, 26 Jul 2004 17:08:43 PDT, Brent Welch said:

>  > 2a) Come up with a clever way to hide or grey out the Spam... menu if
>  > the user hasn't configured it in Preferences.
> 
> This isn't that hard.  It would be easier with an overall
> preference item to "enable spam menu" ... :-)  I may get to this.

There's already a $bogo(inUse) controlling it all, feel free to leverage that.

The hard part is these lines in app-defaults:

*Mops.menulist:         more reply spam
*Mops.g_current:        link move delete reply forward spam
*Mops.g_range:          link move delete forward spam
*Mops.g_nodraft:        reply forward spam

I leveraged that code to do most of the enabling/disabling stuff - the problem
is that Buttons_Current and/or ButtonsGroupState would need an overhaul.
Special-casing the spam menu seemed bletcherous - a better fix would be for
each button to specify not just a label and function, but also an optional
additional TCL variable/expression to evaluate for "enable".

Figuring out how to quote a TCL var/function snippet in app-defaults is left as
an excersize for the reader.  See the botch I made of '*pgpComment'  for an
example of how NOT to do it. :)

_______________________________________________
Exmh-workers mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-workers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFBBaKAcC3lWbTT17ARAmUvAKDIjeJR9ZOvcK4vpbgOZnkcSRLC9QCg9WeJ
PvSVPddexyzjlgVQJaThYoM=
=BPPf
-----END PGP SIGNATURE-----