Re: Consolechars Question
On Tue, Apr 07, 2009 at 08:57:36AM -0400, Thomas H. George wrote: Start mutt like so: chr...@box:~$ LANG=C mutt Once started, type ! then when you see Shell command: type: echo $LANG it should display: C Ah-ha! The response to echo $LANG is en_US.UTF-8 both before and after Weird, indeed!, considering you should have started mutt like so: chr...@box:~$ LANG=C mutt I run consolechars -d. But the problem is not just a mutt problem. For example, the response to sensors is I still wonder why you run consolechars -d as that OVERRIDES any changes you make. Obviously, starting mutt in that way only affects mutt. Try starting mutt without the .muttrc file and try the above again. Since the problem is not very serious and easily corrected by the consolechars -d command I'll just live with it for now. It is a curiosity and if I ever find out the cause I'll be sure to let you know. So mutt DOES display correctly when you run consolechars -d? There is something weird with your setup. Have a look at http://lists.debian.org/debian-user/2008/01/msg00236.html and http://lists.debian.org/debian-user/2008/01/msg00402.html -- Chris. == I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. -- Stephen F Roberts -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Mon, Apr 06, 2009 at 08:57:26AM -0400, Thomas H. George wrote: On Mon, Apr 06, 2009 at 10:42:24PM +1200, Chris Bannister wrote: [Sorry for the late post.] What is the output of: grep -v ^# /etc/console-tools/config BLANK_TIME=30 BLANK_DPMS=off POWERDOWN_TIME=30 APP_CHARSET_MAP=utf8 APP_CHARSET_MAP_vc1=utf8 APP_CHARSET_MAP_vc2=utf8 APP_CHARSET_MAP_vc3=utf8 APP_CHARSET_MAP_vc4=utf8 SCREEN_FONT=uni3-TerninusBold16 OK, same here and: locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8 LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LC_ALL= OK, same here Also if you start mutt like chr...@box:~$ LANG=C mutt You should see the symbols ok? Nope, still the same old funny symbols. That is weird! OK, maybe something in your .muttrc is having an effect. Start mutt like so: chr...@box:~$ LANG=C mutt Once started, type ! then when you see Shell command: type: echo $LANG it should display: C If all that shows up correctly, then I suggest you take this to the mutt-users mailing list. Sorry, but I've run out of ideas. There are some people on mutt-users who have will have more clues than I. -- Chris. == I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. -- Stephen F Roberts -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Tue, Apr 07, 2009 at 08:42:10PM +1200, Chris Bannister wrote: On Mon, Apr 06, 2009 at 08:57:26AM -0400, Thomas H. George wrote: On Mon, Apr 06, 2009 at 10:42:24PM +1200, Chris Bannister wrote: [Sorry for the late post.] What is the output of: grep -v ^# /etc/console-tools/config BLANK_TIME=30 BLANK_DPMS=off POWERDOWN_TIME=30 APP_CHARSET_MAP=utf8 APP_CHARSET_MAP_vc1=utf8 APP_CHARSET_MAP_vc2=utf8 APP_CHARSET_MAP_vc3=utf8 APP_CHARSET_MAP_vc4=utf8 SCREEN_FONT=uni3-TerninusBold16 OK, same here and: locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8 LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LC_ALL= OK, same here Also if you start mutt like chr...@box:~$ LANG=C mutt You should see the symbols ok? Nope, still the same old funny symbols. That is weird! OK, maybe something in your .muttrc is having an effect. Start mutt like so: chr...@box:~$ LANG=C mutt Once started, type ! then when you see Shell command: type: echo $LANG it should display: C Ah-ha! The response to echo $LANG is en_US.UTF-8 both before and after I run consolechars -d. But the problem is not just a mutt problem. For example, the response to sensors is acpitz-virtual-0 Adapter: Virtual device temp1: +40.0°C (crit = +75.0°C) k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: +23.0°C Core0 Temp: +29.0°C Core1 Temp: +27.0°C Core1 Temp: +18.0°C and I recall that the other day reading a man page I found a very weird character being used for bullets. I'd show you what my mutt output is like but I haven't figured out how to capture it. At any rate I appreciate all your suggestions Chris. Since the problem is not very serious and easily corrected by the consolechars -d command I'll just live with it for now. It is a curiosity and if I ever find out the cause I'll be sure to let you know. Best regards, Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Tue, Apr 07, 2009 at 08:57:36AM EDT, Thomas H. George wrote: [..] I'd show you what my mutt output is like but I haven't figured out how to capture it. I use the grab utility from the ezfb tarball - not sure there's a .deb for that. CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
[Sorry for the late post.]
On Sun, Mar 29, 2009 at 10:05:41AM -0400, Thomas H. George wrote:
On Mon, Mar 30, 2009 at 12:55:06AM +1300, Chris Bannister wrote:
That isn't one of the options. Do you mean en_US.UTF-8?
Yes.
Please be careful when pasting in the posts, it is hard to pick config
errors.
Ummm what is the output of:
apt-cache policy {kbd,console-data,console-setup,console-tools}
Interesting. My output is identical to yours except for console-setup
Identical? Surely the http:// entry is different.
which shows 1.28 is installed. Having never used apt-cache policy I read
the man page. From the entry I expected a file /etc/preferences. This
does not exist so I was unsure how to change console-setup.
I had not yet run consolechars -d. I did so and ran the
Why run consolechars -d?
apt-cache policy {kbd,console-data,console-setup,console-tools}
command again. The output was unchanged but the characters used to
indicate threading in mutt and the characters representing bullets in
the output of man apt-cache were changed!
Amusing, what?
It is amusing that you think it would.
What is the output of:
grep -v ^# /etc/console-tools/config
and:
locale
Also if you start mutt like
chr...@box:~$ LANG=C mutt
You should see the symbols ok?
--
Chris.
==
I contend that we are both atheists. I just believe in one fewer god
than you do. When you understand why you dismiss all the other
possible gods, you will understand why I dismiss yours.
-- Stephen F Roberts
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Mon, Apr 06, 2009 at 10:42:24PM +1200, Chris Bannister wrote:
[Sorry for the late post.]
On Sun, Mar 29, 2009 at 10:05:41AM -0400, Thomas H. George wrote:
On Mon, Mar 30, 2009 at 12:55:06AM +1300, Chris Bannister wrote:
That isn't one of the options. Do you mean en_US.UTF-8?
Yes.
Please be careful when pasting in the posts, it is hard to pick config
errors.
Ummm what is the output of:
apt-cache policy {kbd,console-data,console-setup,console-tools}
Interesting. My output is identical to yours except for console-setup
Identical? Surely the http:// entry is different.
which shows 1.28 is installed. Having never used apt-cache policy I read
the man page. From the entry I expected a file /etc/preferences. This
does not exist so I was unsure how to change console-setup.
I had not yet run consolechars -d. I did so and ran the
Why run consolechars -d?
apt-cache policy {kbd,console-data,console-setup,console-tools}
command again. The output was unchanged but the characters used to
indicate threading in mutt and the characters representing bullets in
the output of man apt-cache were changed!
Amusing, what?
It is amusing that you think it would.
What is the output of:
grep -v ^# /etc/console-tools/config
BLANK_TIME=30
BLANK_DPMS=off
POWERDOWN_TIME=30
APP_CHARSET_MAP=utf8
APP_CHARSET_MAP_vc1=utf8
APP_CHARSET_MAP_vc2=utf8
APP_CHARSET_MAP_vc3=utf8
APP_CHARSET_MAP_vc4=utf8
SCREEN_FONT=uni3-TerninusBold16
and:
locale
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
Also if you start mutt like
chr...@box:~$ LANG=C mutt
You should see the symbols ok?
Nope, still the same old funny symbols.
Tom
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Fri, Mar 27, 2009 at 09:30:00AM -0400, Thomas H. George wrote:
On Sat, Mar 28, 2009 at 12:41:03AM +1300, Chris Bannister wrote:
Why consolechars -d? I thought that was already found not to be
satisfactory.
No, consolechars -d always gives me the best font. Since the command
loads the default font it should be loaded at bootup. Instead, as
So everything looks Ok in mutt if you do consolechars -d?
described above, the font changes at least twice during bootup. When
bootup is complete the ASCII characters 1-128 are ok but the ASCII
characters 129-256 are a problem. Double frame symbols are used to
indicate threading instead of single frame symbols and the capital N's
with tilde appear in the lines. The result can be read but it is not
easy to spot where a thread ends and a new subject starts.
How have you set up the locale setting - dpkg-reconfigure locales?
Only en_US_UTF-8 is selected.
That isn't one of the options. Do you mean en_US.UTF-8?
You are running mutt in the virtual console, i.e. non gui, and you are
not ssh'ing from another machine?
I am using command line entries on tty1 through tty6 and I usually start
mutt on tty2.
Same here, and with console-terminus installed and the
Uni3-TerminusBold16 font I can see more foreign characters in mutt.
I am a bit stumped as to why it is not working for you.
Ummm what is the output of:
apt-cache policy {kbd,console-data,console-setup,console-tools}
Mine is:
kbd:
Installed: (none)
Candidate: 1.14.1-4
Version table:
1.14.1-4 0
500 http://debian.attica.net.nz lenny/main Packages
console-data:
Installed: 2:1.07-11
Candidate: 2:1.07-11
Version table:
*** 2:1.07-11 0
500 http://debian.attica.net.nz lenny/main Packages
100 /var/lib/dpkg/status
console-setup:
Installed: (none)
Candidate: 1.28
Version table:
1.28 0
500 http://debian.attica.net.nz lenny/main Packages
console-tools:
Installed: 1:0.2.3dbs-65.1
Candidate: 1:0.2.3dbs-65.1
Version table:
*** 1:0.2.3dbs-65.1 0
500 http://debian.attica.net.nz lenny/main Packages
100 /var/lib/dpkg/status
AIUI, you use either console-tools ** OR ** kbd to set the font.
So if you have 'kbd' installed, I'd purge it and that way you know that
only settings in /etc/console-tools/config are being used.
--
Chris.
==
I contend that we are both atheists. I just believe in one fewer god
than you do. When you understand why you dismiss all the other
possible gods, you will understand why I dismiss yours.
-- Stephen F Roberts
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Mon, Mar 30, 2009 at 12:55:06AM +1300, Chris Bannister wrote:
On Fri, Mar 27, 2009 at 09:30:00AM -0400, Thomas H. George wrote:
On Sat, Mar 28, 2009 at 12:41:03AM +1300, Chris Bannister wrote:
Why consolechars -d? I thought that was already found not to be
satisfactory.
No, consolechars -d always gives me the best font. Since the command
loads the default font it should be loaded at bootup. Instead, as
So everything looks Ok in mutt if you do consolechars -d?
described above, the font changes at least twice during bootup. When
bootup is complete the ASCII characters 1-128 are ok but the ASCII
characters 129-256 are a problem. Double frame symbols are used to
indicate threading instead of single frame symbols and the capital N's
with tilde appear in the lines. The result can be read but it is not
easy to spot where a thread ends and a new subject starts.
How have you set up the locale setting - dpkg-reconfigure locales?
Only en_US_UTF-8 is selected.
That isn't one of the options. Do you mean en_US.UTF-8?
Yes.
You are running mutt in the virtual console, i.e. non gui, and you are
not ssh'ing from another machine?
I am using command line entries on tty1 through tty6 and I usually start
mutt on tty2.
Same here, and with console-terminus installed and the
Uni3-TerminusBold16 font I can see more foreign characters in mutt.
I am a bit stumped as to why it is not working for you.
Ummm what is the output of:
apt-cache policy {kbd,console-data,console-setup,console-tools}
Interesting. My output is identical to yours except for console-setup
which shows 1.28 is installed. Having never used apt-cache policy I read
the man page. From the entry I expected a file /etc/preferences. This
does not exist so I was unsure how to change console-setup.
I had not yet run consolechars -d. I did so and ran the
apt-cache policy {kbd,console-data,console-setup,console-tools}
command again. The output was unchanged but the characters used to
indicate threading in mutt and the characters representing bullets in
the output of man apt-cache were changed!
Amusing, what?
Mine is:
kbd:
Installed: (none)
Candidate: 1.14.1-4
Version table:
1.14.1-4 0
500 http://debian.attica.net.nz lenny/main Packages
console-data:
Installed: 2:1.07-11
Candidate: 2:1.07-11
Version table:
*** 2:1.07-11 0
500 http://debian.attica.net.nz lenny/main Packages
100 /var/lib/dpkg/status
console-setup:
Installed: (none)
Candidate: 1.28
Version table:
1.28 0
500 http://debian.attica.net.nz lenny/main Packages
console-tools:
Installed: 1:0.2.3dbs-65.1
Candidate: 1:0.2.3dbs-65.1
Version table:
*** 1:0.2.3dbs-65.1 0
500 http://debian.attica.net.nz lenny/main Packages
100 /var/lib/dpkg/status
AIUI, you use either console-tools ** OR ** kbd to set the font.
So if you have 'kbd' installed, I'd purge it and that way you know that
only settings in /etc/console-tools/config are being used.
--
Chris.
==
I contend that we are both atheists. I just believe in one fewer god
than you do. When you understand why you dismiss all the other
possible gods, you will understand why I dismiss yours.
-- Stephen F Roberts
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Fri, Mar 27, 2009 at 09:30:00AM EDT, Thomas H. George wrote: [..] Only en_US_UTF-8 is selected. Sounds like a locale/font mismatch. You could try installing the terminus font and see if the consolechars command lets you specify a unicode version of the font: $ apt-cache search terminus $ apt-get install console-terminus $ cd /usr/share/consolefonts $ consolechars Uni3-Terminus12x6.psf.gz # syntax ??? This is what I get with the above font: http://www.geocities.com/fcky1000/fcky/consolemutt.png As you know, I use kbd rather than console-tools and the corresponding setfont command to choose my font. Another possibility if you can't get the console to work satisfactorily is to start a terminal emulation on top of the console. I've had some success with fbiterm - with the added benefit that the (patched) version I'm running supports 256 colors. http://www.geocities.com/fcky1000/fcky/iterm256.png Hope this helps. CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Tue, Mar 24, 2009 at 09:59:57AM -0400, Thomas H. George wrote: On Wed, Mar 25, 2009 at 01:02:42AM +1300, Chris Bannister wrote: On Mon, Mar 16, 2009 at 10:24:47AM -0400, Thomas H. George wrote: During bootup (Lenny) the console font changes to a thin, wiry font and then changes again to a font with much fatter characters. The final font is very readable but when I start mutt the symbols used to indicate threading of messages are weird. OK, install console-terminus then edit /etc/console-tools/config -- /etc/console-tools/config --- # Turn on numlock by default #LEDS=+num APP_CHARSET_MAP=utf8 APP_CHARSET_MAP_vc1=utf8 APP_CHARSET_MAP_vc2=utf8 APP_CHARSET_MAP_vc3=utf8 APP_CHARSET_MAP_vc4=utf8 SCREEN_FONT=Uni3-TerminusBold16 -- /etc/console-tools/config --- The lines # Turn on numlock by default and #LEDS=+num should already be there at the end of the file. Do the threading symbols now show correctly? No, they have become more complex - i.e. the space between the start of a line and the threading symbol is now filled with capital n's with tilde over them. Previously there was just one N with tilde over it at the start of a line. Initially there was no change after editing /etc/console-tools/config as indicated above though echo $LANG responded en.US.UTF-8. I rebooted again seeing the switch to wiry fonts part way through the bootup. When the bootup was complete the console font looked like what I expect from en.US.UTF-8 but when I ran mutt the threading symbols were double line things and the space was filled with the N's with tilde over them. I ran consolechars -d and the threading switched to single line symbols and no N's with tilde. Why consolechars -d? I thought that was already found not to be satisfactory. How have you set up the locale setting - dpkg-reconfigure locales? You are running mutt in the virtual console, i.e. non gui, and you are not ssh'ing from another machine? -- Chris. == I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. -- Stephen F Roberts -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Sat, Mar 28, 2009 at 12:41:03AM +1300, Chris Bannister wrote: On Tue, Mar 24, 2009 at 09:59:57AM -0400, Thomas H. George wrote: On Wed, Mar 25, 2009 at 01:02:42AM +1300, Chris Bannister wrote: On Mon, Mar 16, 2009 at 10:24:47AM -0400, Thomas H. George wrote: During bootup (Lenny) the console font changes to a thin, wiry font and then changes again to a font with much fatter characters. The final font is very readable but when I start mutt the symbols used to indicate threading of messages are weird. OK, install console-terminus then edit /etc/console-tools/config -- /etc/console-tools/config --- # Turn on numlock by default #LEDS=+num APP_CHARSET_MAP=utf8 APP_CHARSET_MAP_vc1=utf8 APP_CHARSET_MAP_vc2=utf8 APP_CHARSET_MAP_vc3=utf8 APP_CHARSET_MAP_vc4=utf8 SCREEN_FONT=Uni3-TerminusBold16 -- /etc/console-tools/config --- The lines # Turn on numlock by default and #LEDS=+num should already be there at the end of the file. Do the threading symbols now show correctly? No, they have become more complex - i.e. the space between the start of a line and the threading symbol is now filled with capital n's with tilde over them. Previously there was just one N with tilde over it at the start of a line. Initially there was no change after editing /etc/console-tools/config as indicated above though echo $LANG responded en.US.UTF-8. I rebooted again seeing the switch to wiry fonts part way through the bootup. When the bootup was complete the console font looked like what I expect from en.US.UTF-8 but when I ran mutt the threading symbols were double line things and the space was filled with the N's with tilde over them. I ran consolechars -d and the threading switched to single line symbols and no N's with tilde. Why consolechars -d? I thought that was already found not to be satisfactory. No, consolechars -d always gives me the best font. Since the command loads the default font it should be loaded at bootup. Instead, as described above, the font changes at least twice during bootup. When bootup is complete the ASCII characters 1-128 are ok but the ASCII characters 129-256 are a problem. Double frame symbols are used to indicate threading instead of single frame symbols and the capital N's with tilde appear in the lines. The result can be read but it is not easy to spot where a thread ends and a new subject starts. How have you set up the locale setting - dpkg-reconfigure locales? Only en_US_UTF-8 is selected. You are running mutt in the virtual console, i.e. non gui, and you are not ssh'ing from another machine? I am using command line entries on tty1 through tty6 and I usually start mutt on tty2. -- Chris. == I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. -- Stephen F Roberts -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Mon, Mar 16, 2009 at 10:24:47AM -0400, Thomas H. George wrote: During bootup (Lenny) the console font changes to a thin, wiry font and then changes again to a font with much fatter characters. The final font is very readable but when I start mutt the symbols used to indicate threading of messages are weird. OK, install console-terminus then edit /etc/console-tools/config -- /etc/console-tools/config --- # Turn on numlock by default #LEDS=+num APP_CHARSET_MAP=utf8 APP_CHARSET_MAP_vc1=utf8 APP_CHARSET_MAP_vc2=utf8 APP_CHARSET_MAP_vc3=utf8 APP_CHARSET_MAP_vc4=utf8 SCREEN_FONT=Uni3-TerminusBold16 -- /etc/console-tools/config --- The lines # Turn on numlock by default and #LEDS=+num should already be there at the end of the file. Do the threading symbols now show correctly? I think that is all that is needed although you might want to check the list archives as this problem has arisen in the past and there may be something I've missed. According to /usr/share/doc/mutt/README.Debian: l10n support If you want to see non-ASCII characters on a Debian system, there's no use fiddling with the variable charset, as described in the manual page muttrc(5). Instead, you'll need to have the Debian package locales installed on your system and set the LANG or LC_CTYPE environment variable. e.g. US users will want to add export LC_CTYPE=en_US to their ~/.bashrc. If you have a /etc/locale.gen file read carefully the comment and do what it says, or it will not work. No, linux systems do not need --enable-locales-fix or --without-wc-funcs, so don't bother me saying these switches cure your problems. BUT I haven't done that and it works fine -- see: chr...@box:~$ echo $LC_CTYPE chr...@box:~$ echo $LANG en_NZ.UTF-8 -- Chris. == I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. -- Stephen F Roberts -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Wed, Mar 25, 2009 at 01:02:42AM +1300, Chris Bannister wrote: On Mon, Mar 16, 2009 at 10:24:47AM -0400, Thomas H. George wrote: During bootup (Lenny) the console font changes to a thin, wiry font and then changes again to a font with much fatter characters. The final font is very readable but when I start mutt the symbols used to indicate threading of messages are weird. OK, install console-terminus then edit /etc/console-tools/config -- /etc/console-tools/config --- # Turn on numlock by default #LEDS=+num APP_CHARSET_MAP=utf8 APP_CHARSET_MAP_vc1=utf8 APP_CHARSET_MAP_vc2=utf8 APP_CHARSET_MAP_vc3=utf8 APP_CHARSET_MAP_vc4=utf8 SCREEN_FONT=Uni3-TerminusBold16 -- /etc/console-tools/config --- The lines # Turn on numlock by default and #LEDS=+num should already be there at the end of the file. Do the threading symbols now show correctly? No, they have become more complex - i.e. the space between the start of a line and the threading symbol is now filled with capital n's with tilde over them. Previously there was just one N with tilde over it at the start of a line. Initially there was no change after editing /etc/console-tools/config as indicated above though echo $LANG responded en.US.UTF-8. I rebooted again seeing the switch to wiry fonts part way through the bootup. When the bootup was complete the console font looked like what I expect from en.US.UTF-8 but when I ran mutt the threading symbols were double line things and the space was filled with the N's with tilde over them. I ran consolechars -d and the threading switched to single line symbols and no N's with tilde. I'll check the archives as you suggested. I think that is all that is needed although you might want to check the list archives as this problem has arisen in the past and there may be something I've missed. According to /usr/share/doc/mutt/README.Debian: l10n support If you want to see non-ASCII characters on a Debian system, there's no use fiddling with the variable charset, as described in the manual page muttrc(5). Instead, you'll need to have the Debian package locales installed on your system and set the LANG or LC_CTYPE environment variable. e.g. US users will want to add export LC_CTYPE=en_US to their ~/.bashrc. If you have a /etc/locale.gen file read carefully the comment and do what it says, or it will not work. No, linux systems do not need --enable-locales-fix or --without-wc-funcs, so don't bother me saying these switches cure your problems. BUT I haven't done that and it works fine -- see: chr...@box:~$ echo $LC_CTYPE chr...@box:~$ echo $LANG en_NZ.UTF-8 -- Chris. == I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. -- Stephen F Roberts -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Mon, Mar 16, 2009 at 06:37:26PM -0400, Chris Jones wrote: On Mon, Mar 16, 2009 at 02:18:40PM EDT, Thomas H. George wrote: [...] maybe, but I have no such command. Sorry .. was in too much of a rush to proofread before posting. The command is showconsolefont and it's part of the kbd package. http://www.geocities.com/fcky1000/fcky/showconsolefont.png Interesting. Installing kbd removed console-tools. With kbd installed showconsolefont displayed the current character set, exactly what I wanted to see. Next I followed the link you gave and googled kbd reaching http://freshmeat.net/projects/kdb but neither site gave any information regarding the tools included in kbd. Returning to a search of Debian packages I learned that console-tools is a replacement for kbd and a package kbd-compat supplies backward compatability so I reinstalled console-tools which removed kbd and then installed kbd-compat. kbd-compat may provide some backward compatability but this does not include showconsolefonts. I returned to a study of the consolechars man page and experimented with the -sfm (screen-font-map) command both bare and with font names supplied from the /usr/share/consolefonts and /usr/share/consoletrans files but failed to find the right combination to get a display of the character set like that generated by kbd's showconsolefont command. Perhaps I am being a little thickheaded in failing to understand the consolechars man page but it seems to me that a couple examples - this is how to display the characters in the current font and this is how you display the characters in a specified font - would not be amiss. Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Consolechars Question
During bootup (Lenny) the console font changes to a thin, wiry font and then changes again to a font with much fatter characters. The final font is very readable but when I start mutt the symbols used to indicate threading of messages are weird. I installed console-tools and found the command consolechars -d changes to a font simple symbols to indicate threading. I don't mind resetting the font after each bootup but I am curious. What font am I using? Is there a way of displaying the available English fonts? Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
Thomas H. George wrote: What font am I using? Is there a way of displaying the available English fonts? What is an 'English font'? Do you mean ascii or Latin? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Mon, Mar 16, 2009 at 10:24:47AM EDT, Thomas H. George wrote: During bootup (Lenny) the console font changes to a thin, wiry font and then changes again to a font with much fatter characters. The final font is very readable but when I start mutt the symbols used to indicate threading of messages are weird. I installed console-tools and found the command consolechars -d changes to a font simple symbols to indicate threading. I don't mind resetting the font after each bootup but I am curious. What font am I using? Is there a way of displaying the available English fonts? $ show consolefont .. may be what you are looking for? CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Mon, Mar 16, 2009 at 01:13:39PM -0400, Chris Jones wrote: On Mon, Mar 16, 2009 at 10:24:47AM EDT, Thomas H. George wrote: During bootup (Lenny) the console font changes to a thin, wiry font and then changes again to a font with much fatter characters. The final font is very readable but when I start mutt the symbols used to indicate threading of messages are weird. I installed console-tools and found the command consolechars -d changes to a font simple symbols to indicate threading. I don't mind resetting the font after each bootup but I am curious. What font am I using? Is there a way of displaying the available English fonts? $ show consolefont .. may be what you are looking for? CJ maybe, but I have no such command. locale says LANG=en_US.UTF-8, I didn't think to check the output of locale before issuing the consolechars -d command. I will do so after the next reboot. I normally shutdown the system every night. Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Consolechars Question
On Mon, Mar 16, 2009 at 02:18:40PM EDT, Thomas H. George wrote: [...] maybe, but I have no such command. Sorry .. was in too much of a rush to proofread before posting. The command is showconsolefont and it's part of the kbd package. http://www.geocities.com/fcky1000/fcky/showconsolefont.png CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
