FYI: It looks like I may finally have the time to work on muttzilla
again. I'm setting up muttzilla with sourceforge. -users and
-announce mailing lists are up, but the CVS repository hasn't been
populated yet. Hopefully there will be a slightly more user-friendly
version available soon.
Anyway, Brad's questions...
On Fri, Jul 28, 2000 at 06:42:21PM -0500, Brad Cramer wrote:
> Is anyone suing muttzilla with Eterm? I am having a heck of a time getting
I don't remember hearing from anyone who is using Eterm, but that
doesn't mean much.
> it configured to work properly. I set mailterm=Eterm in my muttzilla.conf
> file it starts and work but I get an error box (I think these errors have to
> do With Eterm)
What does the error box say? My guess is that Eterm doesn't accept
the same arguments as xterm and clones (like rxvt), and is choking on
them.
> I try to set mailterm=Eterm -t mutt which is how I normaly
> call mutt but I get an error about expecting = but gettin -t instead. If
> someone could give me some ideas I would be thankful.
That definitely won't work. To get the effect you desired from a
parsing standpoint, you would need to quote it like this:
mailterm="Eterm -t mutt"
However, please don't do that. You would find that the argument
handling doesn't behave the way you want it to behave. That mailterm
line will cause mzmail.{py,sh} to attempt to execute a program named
Eterm\ -t\ mutt. I doubt that is what you intend.
[Installing an Eterm rpm...`man Eterm`...]
Well, -t ("load theme") is definitely something normal xterm doesn't
do. You have stumbled upon the reason why muttzilla.so does as little
as possible, handing off most of the interesting work to a wrapper
script: it will be relatively easy for you to hack up mzmail.{py,sh}
to properly spawn your Eterm, or to ditch mzmail.{py,sh} entirely and
write your own simple wrapper script that just spawns mutt in an Eterm
for you.
Brian
