Yeah, exporting LANG to en_US.UTF-8 and calling locale again should help.
You are using a 7-bit locale, trying to edit UTF-8 (or even 8-bit)
files, you'd get all kinds of weird results.
Thanks, I will try that.
___
macports-users mailing list
On Thu, Sep 17, 2009 at 11:41 AM, Max Brown max.e.br...@gmail.com wrote:
Yeah, exporting LANG to en_US.UTF-8 and calling locale again should help.
You are using a 7-bit locale, trying to edit UTF-8 (or even 8-bit)
files, you'd get all kinds of weird results.
It works now. Thanks
Hi,
I am having some problems with vim and unicode files.
If I create a file test.txt with some random text in it, then open it
in vim, :set encoding=unicode, and save, then strange things happen:
$ cat test.txt
123
123
max:~ max$ file test.txt
test.txt: ASCII text
max:~ max$ vim test.txt
max:~
Ryan Schmidt wrote:
MacPorts is designed to not use any software installed outside of
MacPorts (with a few exceptions), hence manually installing ghc in
/usr/local is expected to have no effect.
There are existing bugs on ghc filed in the issue tracker:
Hi,
I just tried installing ghc on my new Macbook Pro, and get:
$ sudo port install ghc
--- Configuring ghc
Error: Target org.macports.configure returned: configure failure:
shell command cd
Thanks, that was a good idea - seems to have worked.
On 3/7/07, Daniel J. Luke [EMAIL PROTECTED] wrote:
On Mar 7, 2007, at 12:31 PM, Max Brown wrote:
How did I manage to break this? Are the files in my package directory
worthless now?
You didn't break it. Archive mode just doesn't do quite
