Re: [vile] I've got my 'wide' characters display problem back - in 9.7z

[Chris G]

On Fri, Jan 29, 2010 at 07:01:17AM -0500, Thomas Dickey wrote:
> On Thu, Jan 28, 2010 at 12:27:20PM +0000, Chris G wrote:
> > On Thu, Jan 28, 2010 at 12:25:43PM +0000, Chris G wrote:
> > > On Thu, Jan 28, 2010 at 12:14:01PM +0000, Chris G wrote:
> > > > > Beyond that - I diagnose most of the problems by configuring 
> > > > > --with-trace,
> > > > > and looking at the Trace.out file when running it.  That's large, 
> > > > > unless
> > > > > one uses an empty .vilerc file.  (If the problem is in the .vilerc 
> > > > > file,
> > > > > then I pare that down to just the problem before wading through 4Mb
> > > > > of traces...).
> > > > > 
> > > > I've removed my .vilerc file and the problem is still there.  I'll
> > > > configure with --with-trace and take a look.
> > > > 
> > > > > The basic locale initialization is near the beginning, but the 
> > > > > decision of
> > > > > whether the buffer should be utf8 (probably not the problem) is at
> > > > > the end.
> > > > > 
> > > Well here's the result (attached) of running a vile built with
> > > --with-trace, I just opened a file with a few UK pound signs and
> > > accented characters and did nothing more. The characters are displayed
> > > as \u00A3 and \u00E9 still. I can't see anything particularly wrong
> > > with the Trace.out but that's probably just my lack of a full
> > > understanding of it.
> > > 
> > > The characters *do* display correctly if I just cat the file so the
> > > terminal is quite capable of displaying them.
> > > 
> > .... and of course I forgot to attach it!  :-)
> 
> I see this is a case discussed before - vile is looking for a locale that
> isn't installed.  But that was a while back.  Here's a first cut for a
> new feature that addresses the problem (seems to work here...)
> 
Yes, fixed, thanks very much!  

I guess modern/newish Linux distributions don't have a narrow locale
installed at all nowadays which is what has provoked this issue.

-- 
Chris Green