<<< Date Index >>>     <<< Thread Index >>>

Re: Mutt 1.5.14 on Freebsd Display Problem



Udo Schweigert <mutt@xxxxxxxxxxxxxxx> said:
> On Thu, Mar 01, 2007 at 21:04:18 -0800, Ryan Phillips wrote:
> > Paul Walker <paul@xxxxxxxxxxxxxxxxxxxxx> said:
> >> On Thu, Mar 01, 2007 at 01:23:28PM -0800, Ryan Phillips wrote:
> >> 
> > >> This problem didn't happen with 1.5.13.  If it makes a difference I'm
> > >> using putty to ssh into the box.
> >> 
> >> I seem to remember having that problem when putty and the terminal had
> >> different ideas about what encoding to use. I solved it by setting putty to
> >> using UTF-8. Might be worth you trying the same, just in case...
> >> 
> > 
> > Hi Paul,
> > 
> > Thanks for the reply.  I have the same problem with iTerm on OSX
> > connecting to the same Freebsd box.  
> > 
> > I narrowed down the problem with ncurses.  I had WITH_MUTT_NCURSES=yes
> > set in my /etc/make.conf file.  Removing the line and letting mutt
> > compile with the default slang library fixed the problem.
> 
> Was your ncurses port compiled with WITHOUT_WIDEC set? Or has it been
> compiled on a 5.x-machine as wide-character support only works on 6.x?
> 

This was a fresh install of 6.0, and no, WITHOUT_WIDEC, was never
enabled.

-Ryan