Doctor Who wrote:
On Wed, Jan 14, 2009 at 2:57 AM, Joshua Root j...@macports.org wrote:
.
There are a couple of relevant settings in Terminal.app's preferences
which may be preferable to setting LANG manually.
- Josh
Such as?
Such as the International section in the Advanced tab.
-
On Jan 14, 2009, at 10:06, Joshua Root wrote:
Doctor Who wrote:
On Wed, Jan 14, 2009 at 2:57 AM, Joshua Root wrote:
There are a couple of relevant settings in Terminal.app's
preferences
which may be preferable to setting LANG manually.
Such as?
Such as the International section in
Ryan Schmidt wrote:
On Jan 14, 2009, at 10:06, Joshua Root wrote:
Doctor Who wrote:
On Wed, Jan 14, 2009 at 2:57 AM, Joshua Root wrote:
There are a couple of relevant settings in Terminal.app's preferences
which may be preferable to setting LANG manually.
Such as?
Such as the
On Jan 14, 2009, at 18:12, Joshua Root wrote:
Ryan Schmidt wrote:
On my Tiger system I have in Terminal's Inspector window a Display
section where I can set the Character Set Encoding (and I have it
set to
Unicode UTF-8). I understood that I must then set the LANG
variable to
correspond
On Tue, Jan 13, 2009 at 1:06 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Jan 11, 2009, at 14:13, Doctor Who wrote:
I installed the findutils and coreutils packages so that I could use
locate on my Mac.
FYI, locate works fine on my Mac without installing anything extra with
On Jan 13, 2009, at 08:50, Doctor Who wrote:
On Tue, Jan 13, 2009 at 1:06 AM, Ryan Schmidt wrote:
On Jan 11, 2009, at 14:13, Doctor Who wrote:
I installed the findutils and coreutils packages so that I could use
locate on my Mac.
FYI, locate works fine on my Mac without installing
On Jan 11, 2009, at 14:13, Doctor Who wrote:
I installed the findutils and coreutils packages so that I could use
locate on my Mac.
FYI, locate works fine on my Mac without installing anything extra
with MacPorts... I'm on Tiger, though I've probably enabled something
somewhere along the
