[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vile] vile-9.6j.patch.gz

From: Chris G
Subject: Re: [vile] vile-9.6j.patch.gz
Date: Wed, 26 Mar 2008 13:36:45 +0000
User-agent: Mutt/1.5.17 (2007-11-01)

On Wed, Mar 26, 2008 at 08:34:36AM -0400, Thomas Dickey wrote:
> On Wed, 26 Mar 2008, Chris G wrote:
>> I don't quite follow this.  Maybe I didn't explain my case right.  It
>> should be impossible (as I understand it) to create a file with
>> iso-8859-1 pound signs in it if everything is set up correctly for
>> utf-8 shouldn't it?  I just happened to have some iso-8859-1 pounds in
>> a file I had created earlier.
>> When I edited the file with the iso-8859-1 pound signs (just 0xA3
>> bytes by themselves) I got the incorrect cursor positioning. These are
>> invalid characters in utf-8 and, I believe, vile should really display
>> the 'invalid character' glyph which on my system appears to be an
>> inverse question mark.
> oh.  If you're editing a non-utf8 file that you've told vile _is_ utf8,
> then it's supposed to display the illegal codes as something like \?A3
> (enough to make them visible, but not simple to edit, since the keyboard
> input tries to grab complete characters).
Yes, that's what I'm doing I think.  I have "set file-encoding=utf-8"
and there are some non utf8 characters in the file.  They're just
being displayed as pound signs even though they're not really (in
utf-8 anyway).

>>> (by the way - on Solaris I got good results using the terminfo driver.
>>> curses might work if it's linked with the xpg4 library, though I know
>>> that library has some breakage in the time-delays).
>> Ah, thank you, I'd forgotten that I probably want a Solaris vile too.
>> I don't run vile on Solaris as much as I did now that I have a Linux
>> desktop system which sees all the same filesystems that the Solaris
>> boxes can see.
> I have shell access to one Solaris that has UTF-8 locales installed - 
> enough to test this (no X forwarding, so I cannot test xvile there).
Well I've built vile 9.6j on our Solaris 2.6 system (which is where I
need it occasionally) and it runs OK.  I'm not sure if the locales are
set up right there but there does *appear* to be an en_US.UTF-8 there.

I've forced everything to en_US.UTF-8 by using LC_ALL:-

    crusade$ locale

... and now vile won't start at all:-

    crusade$ vile
    cannot setup translation from ISO8859-1 to UTF-8

Does this suggest the en_US.UTF-8 isn't properly installed or is it
something (e.g. iconv) that vile needs that isn't working?  With the
locale left at its default (probably some breed of iso-8859) vile runs
OK so it's not a problem really, I don't actually *need* utf-8 on

Chris Green

reply via email to

[Prev in Thread] Current Thread [Next in Thread]