public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question regarding UTF-8 settings
Date: Sun, 28 Aug 2011 18:33:27 +0200	[thread overview]
Message-ID: <20110828163327.GA10160@solfire> (raw)
In-Reply-To: <201108281652.17003.michaelkintzios@gmail.com>

Mick <michaelkintzios@gmail.com> [11-08-28 18:08]:
> On Sunday 28 Aug 2011 12:41:54 meino.cramer@gmx.de wrote:
> > Mick <michaelkintzios@gmail.com> [11-08-28 13:08]:
> > > On Sunday 28 Aug 2011 09:51:36 meino.cramer@gmx.de wrote:
> > > > Hi,
> > > > 
> > > > following this guide:
> > > > http://www.gentoo.org/doc/en/utf-8.xml
> > > > 
> > > > Doing a
> > > > 
> > > >     locale -a | grep de_DE | grep utf
> > > > 
> > > > I got:
> > > >     de_DE.utf8
> > > > 
> > > > .
> > > > 
> > > > Then I created the file
> > > > 
> > > >     /etc/init.d/02locale
> > > 
> > > Hmm ... you probably want to create /etc/env.d/02locale instead.
> > > 
> > > Then set in it:
> > > 
> > > LC_LANG=de_DE.utf8
> > > 
> > > and perhaps:
> > > 
> > > LC_TIME="POSIX"
> > > LC_COLLATE="C"
> > > 
> > > and things should hopefully work out as intended after you run env-update
> > > or logout/login.
> > 
> > Hi Mick,
> > 
> > ....I did create /etc/env.d/02locale...I only confused it in my
> > posting...
> > 
> > Now I have changed, what you have suggested, but  mutt still has
> > problems with the "arrows" when displaying threads.
> > Is there any other fix known regarding mutt?
> 
> Although I'm using mrxvt as a terminal I do not use mutt.  Where is mutt 
> picking up its encoding for those arrows?  Could it be that they are hard 
> coded somehow in it?  Sorry I can't suggest anything more useful on this 
> problem ...
> 
> -- 
> Regards,
> Mick

Hi Mick,

I switched from mrxvt, which gets screwed up when compiled from svn
(the only source for a mrxvt, which a part of unicode support) and 
confronted then with some key combos like CTRL-SHIFT-UPARROW, to urxvt,
which understands unicode fully, but has "only" a basic tabbed
support. This fixes the locks.

For the other problem, the arrows in threads, I instructed mutt to 
use ASCII-symbols like +-> or \-> instead, which looks a little retro,
but may be this will correspond to the IBM Model M keyboard I use (and
like so much ;).

It just like being retro-progressive: Take the best of both worlds:
Run a AMD-hexacore-PC, use Gentoo with openbox, avoid graphically
gimmicks (no punt intended!), avoid using the mouse, get used to use
vim, sed, awk, col, cmp, diff, join, uniq, fmt and such to their full
power and do all this with a 20 year old keyboard, which looks like
new. ;)

Its feeling like MyGyver inventing the IT-industry from a soldering
iron, a 80x40 charakter terminal and a 386 processor, hahahahaha!

All this not really meant /THAT/ seriously... :)

Best regards and have a nice "whatever time of the day you
currently may have" .
mcc




  reply	other threads:[~2011-08-28 16:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-28  8:51 [gentoo-user] Question regarding UTF-8 settings meino.cramer
2011-08-28  9:06 ` Andrea Conti
2011-08-28 10:59   ` meino.cramer
2011-08-28 10:33 ` Mick
2011-08-28 11:41   ` meino.cramer
2011-08-28 15:51     ` Mick
2011-08-28 16:33       ` meino.cramer [this message]
2011-08-28 12:52 ` Volker Armin Hemmann

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=20110828163327.GA10160@solfire \
    --to=meino.cramer@gmx.de \
    --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