bug-ncurses
[Top][All Lists]
Advanced

[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 05:04:01 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Sep 20, 2017 at 10:52:53AM +0200, Dr. Werner Fink wrote:
> On Wed, Sep 20, 2017 at 04:37:36AM -0400, Thomas Dickey wrote:
> > On Wed, Sep 20, 2017 at 09:13:33AM +0200, Dr. Werner Fink wrote:
> > > On Tue, Sep 19, 2017 at 04:30:03PM -0400, Thomas Dickey wrote:
> > ...
> > > > As an aside: ncurses won't try to repeat non-ASCII codes, because the
> > > > existing logic for UTF-8 vs ASCII line-drawing in ncurses would have to
> > > > be integrated with the "rep" (and if you read through PutAttrChar, 
> > > > you'll
> > > > see why I didn't do it yet).
> > > 
> > > Taken ... I see that `tput rep' only work with the ASCII value of the 
> > > VT100
> > > name of the glphys but not with the ASCII sign like `-' or the VT100 name
> > > its self like `p'
> > > 
> > >   for glpyh in 112 113 114 115; do
> > >   tput -S <<-!
> > >   smacs
> > >   rep $glpyh 20
> > >   rmacs
> > >   !
> > >   done
> > > 
> > > works but using `p q r s' does lead to error signs in XTerm
> > 
> > I don't see that here (see attached screenshot).
> 
> 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...

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://ftp.invisible-island.net

Attachment: signature.asc
Description: Digital signature


reply via email to

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