Re: [gentoo-user] Re: mc-4.6.1 not showing graphical characters in terminal

[Jerry McBride <mcbrides9@comcast.net>]

On Saturday 09 September 2006 19:01, Peter wrote:
> On Sat, 09 Sep 2006 17:55:35 -0400, Jerry McBride wrote:
> > On Saturday 09 September 2006 16:02, Peter wrote:
> >> After
> >> 1) upgrade to gcc 4.1.1
> >> 2) upgrade to profile 2006.1
> >> 3) revdep-rebuild recompile for libstdc++ and for new profile uses
> >> (which included mc)
> >>
> >> Now, issuing mc at a terminal prompt (not inside X) shows no border
> >> characters. Does this have something to do with unicode support? The
> >> only way I can get any useful terminal output is to use the -a output
> >> for stick characters. Inside an xterm or similar, mc shows graphical
> >> characters fine. I re-emerged mc with -unicode, but the results are the
> >> same.
> >>
> >> Clues?
> >
> > Yup...
> >
> > I had the same MC issue after upgrading to the 2006.1 levels. It's a very
> > basic language issue. I'm not sure if it's gcc, glibc or perhaps an xorg
> > module...
> >
> > Prior to this upgrade, I never gave language setting a second thought...
> > but once mc began acting up, I started digging around with google and
> > this is what I cobbled up.
> >
> > In "/etc/env.d/02locale " I have set: LC_ALL="en_US.ISO-8859-1"
> > In "/etc/rc.conf" I set "UNICODE=no"
> > In "/etc/conf.d/consolefont" I have set:
> > CONSOLETRANSLATION=8859-1_to_UNI"
> >
> > That last line makes no since to me, but it seems to be required for MC.
> >
> > Last but least run env-update, source /etc/profile and check
> > /etc/profile.env has LC_ALL set to "en_US.ISO-8859-1". It may take a
> > reboot, but once I had made the change, midnight commander began drawing
> > lines again.
> >
> > The only other problems I ever had with MC is, if I leave mc running for
> > any length of time, it begins to take more and more cpu resource... Top
> > will show like 80% useage. Once I kill off mc, everything is back to
> > normal. Anyone have a tip for that one?
> >
> > Jerry...
> >
> > P.S. I welcome all comments.
>
> It required a reboot although I think I could have run console manually.
> Turning off UNICODE and enabling the cache translation setting as you
> suggested worked. This needs to be documented. Jerry, would you like to
> add your comments to the bug? I'd like to see you credited for your help.
>

Hi Peter,

I just had a look at the bug report and comment #5 from Jakub Moc is the 
correct fix. 

I'll chime in and post my thoughts anyway...


Jerry
-- 
gentoo-user@gentoo.org mailing list