Skip to main content

Midnight Commander not displaying properly in mrxvt

I think the problem here is not really directly related to Mrxvt not supporting unicode since MC does not fully support Unicode either. The problem I think is that Debian Etch (4.0) is shipped with Unicode support enabled by default. In fact locale shows that encoding is by default set to UTF-8. Now, to get a better display of MC, we need to make some minor adjustments. First, open terminal, like xterm or Eterm, then change to root user and do the following:
#: dpkg-reconfigure --force locales
Select locales you need to be installed/configured in your system. Then select, for example, en_US.ISO-8859-15. This will configure your system to use ISO-8859-15 encoding by default. Restart computer and off you go. ~ts

Comments

Nose said…
great!
many thanks for the advice. Worked quite good for me.
Anonymous said…
thank you so much! This was probably the only thing holding me back from using mrxvt, and it actually helps out with a bunch more then just mrxvt.

Popular posts from this blog

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re