special characters and how they are represented
From: Michael W. Oliver (michael_at_gargantuan.com)
Date: 04/22/05
- Previous message: Eric Buchanan: "Linux-opera takes forever to open"
- Next in thread: Joel: "Re: special characters and how they are represented"
- Reply: Joel: "Re: special characters and how they are represented"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 21 Apr 2005 19:14:14 -0400 To: questions@freebsd.org
hi folks. this may seem uber-simple to some of you, but i'm ignorant
regarding this. your help is appreciated.
so, i have this album from Mötley Crüe (that looks right in vim, my
editor for mutt), and i have ripped it to FLAC and put it on my file
server. on the server, however, the directory name doesn't look like
that. well, it does if i pipe ls through more (ls | more). here are
the scenarios:
1) ls --> this shows "M?tley_Cr?e" as directory name
2) ls | more --> this looks right, with umlaut over o and u
3) ls M<TAB> --> this shows "M\366tley_Cr\374e" (backslash366 &
backslash374, respectively), using csh as my shell w/set complete and
set autolist
my question is... why the differences? is there a way to force
consistent behavior across all three scenarios?
thanks in advance.
-- Mike Oliver [see complete headers for contact information]
- application/pgp-signature attachment: stored
- Previous message: Eric Buchanan: "Linux-opera takes forever to open"
- Next in thread: Joel: "Re: special characters and how they are represented"
- Reply: Joel: "Re: special characters and how they are represented"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
