Re: dialog-1.3-20180621 displays ugly black bars on FreeBSD

[Alan Somers]

Somebody needs to prepare a patch that imports the new cdialog into the contrib/ area and test it.  You can take the lead, if you want, and then open up a review at reviews.FreeBSD.org.

-Alan

On Mon, Aug 17, 2020 at 12:27 PM David Boyd <David.Boyd49@twc.com> wrote:

On Mon, 2019-02-11 at 05:20 -0500, Thomas Dickey wrote:
> On Sun, Feb 10, 2019 at 06:18:43PM -0700, Alan Somers wrote:
> > On Sun, Feb 10, 2019 at 6:05 PM Thomas Dickey <dickey@his.com> wrote:
> > >
> > > On Sun, Feb 10, 2019 at 03:39:11PM -0700, Alan Somers wrote:
> > > > Prior to 1.3-20180621 dialog would fill unused space at the end of the
> > > > line with the background color.  However, starting with 1.3-20180621
> > > > it doesn't.  Instead, it seems to fill with whatever the terminal's
> > > > background color was prior to starting dialog.
> > > >
> > > > Steps to reproduce on FreeBSD current:
> > > > cat /etc/rc.conf | dialog --programbox 23 76
> > > >
> > > > With older versions of dialog the box's background is a consistent
> > > > color.  With 1.3-20180621 and newer, the trailing unused part of each
> > > > line is filled with (on my terminal at least) black.
> > >
> > > hmm - in a quick check here with dialog 1.3-20181107 running in screen
> > > or xterm, both white-background, I'm not seeing that problem - it fills
> > > with color.  (The changes in dialog since 20180621 were just portability
> > > fixes in the configure script).
> > >
> > > What was the previous good version of dialog?
> > > I'd assume that was 1.3-20171209
> >
> > Yes.  I've tried that one and several earlier ones too, and they're all fine.
> >
> > >
> > > Also, what terminal (and $TERM value)?
> >
> > Both the console (TERM=xterm) and xfce4-terminal (TERM=xterm-256color)
> > show the problem.  However, alacritty (TERM=xterm-256color) works
> > fine.
> >
> > >
> > > (I don't have a FreeBSD current, but do have 11 and 12 release,
> > > to investigate).
> >
> > I see the problem on 12.0-RELEASE as well.
>
> I can see a problem (will determine where it's coming from, this evening).
>
Thomas and Alan,

Now that a fix for cdialog has been committed, what is the next step toward getting dialog fixed in head (13.0-CURRENT)?

Let me know what I can do.

Thanks.

David Boyd.