On Thursday, 18 August 2005, at 15:44:59 (-0400),
Mike Frysinger wrote:
> hints on how to debug further ?
> LC_ALL=en_US Eterm -> OK
> LC_ALL=en_US.UTF-8 Eterm -> not OK
>
> watching top shows that xfs is eating the CPU, not Eterm ...
Try using non-ISO-10646 fonts. I remember this having someth
On Thursday 18 August 2005 10:33 am, Michael Jennings wrote:
> On Monday, 15 August 2005, at 13:28:39 (+1000),
>
> Dave Novakovic wrote:
> > Hve been reccomended to submit a bug report to this email addie.
> >
> > Using locale en_AU.utf8 causes eterm to start very slowly, the whole
> > time it is l
On Monday, 15 August 2005, at 13:28:39 (+1000),
Dave Novakovic wrote:
> Hve been reccomended to submit a bug report to this email addie.
>
> Using locale en_AU.utf8 causes eterm to start very slowly, the whole
> time it is loading it uses 100% cpu, and pretty much puts my system in
> stop mode.
On Mon, 15 Aug 2005 13:28:39 +1000
Dave Novakovic <[EMAIL PROTECTED]> wrote:
> Hve been reccomended to submit a bug report to this email addie.
>
> Using locale en_AU.utf8 causes eterm to start very slowly, the whole
> time it is loading it uses 100% cpu, and pretty much puts my system
> in stop
I noticed something like this as well using en_US.utf8, but I chalked
it up to something I had messed with.
On 8/14/05, Dave Novakovic <[EMAIL PROTECTED]> wrote:
> Hve been reccomended to submit a bug report to this email addie.
>
> Using locale en_AU.utf8 causes eterm to start very slowly, the wh
Hve been reccomended to submit a bug report to this email addie.
Using locale en_AU.utf8 causes eterm to start very slowly, the whole
time it is loading it uses 100% cpu, and pretty much puts my system in
stop mode. With RiverRat's help i was able to make an alias to ignore
the locale for eter
