[Top][All Lists]

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

Re: Tabstop width not reset by reset command, or hardcoded to wrong widt

From: Thomas Dickey
Subject: Re: Tabstop width not reset by reset command, or hardcoded to wrong width
Date: Sat, 25 May 2019 15:17:38 -0400
User-agent: Mutt/1.5.23 (2014-03-12)

On Wed, May 22, 2019 at 03:16:52PM +0545, Vincent Huisman wrote:
> Small remark on the original bug thread:
> > curses (SVr4 curses, ncurses, NetBSD)
> > all provide a library variable TABSIZE which an application could set to
> > reflect a tab-size which was set externally.  Otherwise, they all use the
> > initial-tabs value from the terminal database.
> I found that TABSIZE as well as init_tabs are used. In case
> TABSIZE!=init_tabs it is used to calculate where to place the cursor and
> that blows up when using hard tabs. I might be wrong, but this is my
> observation.

actually that's misleading: NetBSD tput doesn't initialize tabstops:


Interestingly enough, Solaris tput also doesn't:


But further,
the chunk in the ncurses source we're discussing was from ESR,
who adapted mytinfo, and according to the comment, got rid
of some extra logic using cursor-movement (which I see in mytinfo).


However, the code itself looks like the BSD code that Solaris uses.


I rewrote the chunk, dropping the comment, and the result will be in today's

(by the way, your messages would be easier to read, with some whitespace)

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

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