[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] [PATCH] Make xterm usage configurable

From: Eric Gillespie
Subject: Re: [Nmh-workers] [PATCH] Make xterm usage configurable
Date: Fri, 15 Aug 2008 12:04:58 -0700

Oliver Kiddle <address@hidden> writes:

> Eric Gillespie wrote:
> > The default behavior of throwing new xterms at me out of nowhere
> > is horribly annoying.
> Does anyone still have it configured to do that instead of having it
> just invoke iconv, recode or similar.

I sure don't, but I've always removed mhn.defaults.  As I said,
this is how it works out of the box, and that sucks.

> That's not to say that that's easy. Combine a setting for
> mhshow-show-text/html and mhshow-charset-iso-8859-1 and the codeset
> script needs to see that it's second argument contains spaces so is
> probably a command and eval it. And some such commands have their own
> charset handling.

I don't know what you're saying.  Certainly things work just fine
without this setting, even viewing html attachments.

> I'm not overly enthusiastic about the change adding a configure option. Only
> longtime nmh users are going to know what they're doing in specifying
> the option and they could easily use a different solution like setting
> several mhshow-charset-* options in their configuration.

Let's be honest, there are only longtime nmh users.  nmh is the
poster child for grognardware.  The reason I did it this way was
to cater to the longtime users.  If it were up to me, I'd just
remove this line from mhn.defaults entirely.  Maybe I shouldn't
have just assumed that would be shot down.  What do folks think?

Eric Gillespie <*> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]