zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <borsenkow.msk@sni.de>,
	"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Re: BUG: Impossible TIOCGWINSZ rows/cols
Date: Tue, 22 Jun 1999 16:33:43 +0000	[thread overview]
Message-ID: <990622163343.ZM29267@candle.brasslantern.com> (raw)
In-Reply-To: <006601bebca3$780f1ca0$21c9ca95@mow.siemens.ru>

On Jun 22,  3:36pm, Andrej Borsenkow wrote:
} Subject: BUG: Impossible TIOCGWINSZ rows/cols
}
} I just got it (with all patches):
} 
} BUG: Impossible TIOCGWINSZ rows
} BUG: Impossible TIOCGWINSZ cols
} 
} This is using dtterm under TED 4.2.

This means (as you might guess) that my new LINES/COLUMNS code expected
to be able to read the terminal size from the tty driver and got back a
non-positive value (probably zero).  I knew this sometimes occured on Sun
and BSD operating systems back when I was using them regularly, but I was
not sure it still did.

The code grabs the termcap (terminfo) rows/cols values in this case, or
uses 24/80 if the term database doesn't have values.

If (1) this happens only on startup and not when you resize the window,
and (2) the LINES/COLUMNS values you're getting are correct, then you can
just ignore the message.  (You get the warning only if you compile with
debugging.)  If (1) is false, I'm not sure what to do; the only reasonable
thing may be to take out the debug warning and simply ignore the problem.
If (2) is false, you'll have to compensate in your startup files by using
the dtterm equivalent of `eval $(resize)`.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~1999-06-22 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-22 11:36 Andrej Borsenkow
1999-06-22 16:33 ` Bart Schaefer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=990622163343.ZM29267@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=borsenkow.msk@sni.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).