[Top][All Lists]

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

Re: [bug-ncurses] How to use `rep' in xterm since ncurses-6.0-20170729

From: Thomas Dickey
Subject: Re: [bug-ncurses] How to use `rep' in xterm since ncurses-6.0-20170729
Date: Wed, 20 Sep 2017 19:41:42 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Sep 20, 2017 at 02:33:03PM +0200, Dr. Werner Fink wrote:
> On Wed, Sep 20, 2017 at 05:04:01AM -0400, Thomas Dickey wrote:
> > On Wed, Sep 20, 2017 at 10:52:53AM +0200, Dr. Werner Fink wrote:
> > > 
> > > I meant that I see exactly the same within XTerm with 112 113 114 115
> > > but not with p q r s
> > 
> > That's because tput doesn't know how to convert "p q r s" into numbers.
> > I could make it report an error and quit...
> Stupid question: does hline(), hline(), mvhline(), and mvvline() use
> repeat_char if found in the current terminfo entry?  And how do those
> functions the given character, e.g. ' ' or '-' ...

The repeat function is done at a low level, as ncurses translates screen
updates to escape sequences.

This chunk in tty_update.c is what decides if the repeat is used:

                    } else if (repeat_char != 0 &&
                               (!SP_PARM->_screen_unicode &&
                                ((AttrOf(ntext0) & A_ALTCHARSET) == 0 ||
                                 (CharOf(ntext0) < ACS_LEN))) &&
                               runcount > SP_PARM->_rep_cost) {
Essentially it says that if there's enough repetition on a horizontal
line (no verticals...), and the previous cell on the screen is a
narrow character, then it's okay to repeat that.

> I've reports about ncdu (NCurses Disk Usage) as well as about other
> ncurses based applications about wrong/missing line drawings

If it's for ncurses 20170829 or later and xterm (any recent version),
I can address that.

For those other terminal emulators - the developers have been advised
repeatedly that setting TERM=xterm (or anything derived from xterm) is a bad
idea.  We'll have similar discussions in the future.

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

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