From: "Peter" <sw98234@hotmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: mc-4.6.1 not showing graphical characters in terminal
Date: Sat, 9 Sep 2006 22:55:52 +0000 (UTC) [thread overview]
Message-ID: <edvgpo$uo5$1@sea.gmane.org> (raw)
In-Reply-To: 200609091755.35304.mcbrides9@comcast.net
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.
>
http://bugs.gentoo.org/show_bug.cgi?id=146990
This is tough. I filed a bug. Obviously, with unicode a new can of worms
has been opened. I have slang, ncurses, etc. I did not change the default
console fonts but am afraid I will have to. ITMT, mc -a will have to do.
Thanks for the feedback. Feel free to chime in on the bug. Jakub is in his
worksforme mode.
--
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via
jabber: pete4abw at jabber.org
ICQ: 73676357
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-09 23:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 20:02 [gentoo-user] mc-4.6.1 not showing graphical characters in terminal Peter
[not found] ` <45032BAF.8020309@gmx.net>
2006-09-09 21:09 ` [gentoo-user] " Stefan Wimmer
2006-09-09 21:55 ` [gentoo-user] " Jerry McBride
2006-09-09 22:55 ` Peter [this message]
[not found] ` <edvh56$vh0$1@sea.gmane.org>
2006-09-10 1:31 ` [gentoo-user] " Jerry McBride
2006-09-10 11:18 ` Peter
2006-09-10 14:55 ` Bo Ørsted Andresen
2006-09-10 15:46 ` Peter
2006-09-10 16:44 ` Bo Ørsted Andresen
2006-09-10 16:34 ` Jerry McBride
2006-09-10 13:33 ` Peter
2006-09-10 15:16 ` [gentoo-user] " Lukasz Pawelczyk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='edvgpo$uo5$1@sea.gmane.org' \
--to=sw98234@hotmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox