zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: braemer@doc.physi.uni-heidelberg.de (Achim Braemer)
Cc: zsh-workers@math.gatech.edu (Zsh workers list)
Subject: Re: Problem with xterm, zsh-2.6Beta20 and OSF/1
Date: Thu, 20 Jun 1996 01:21:46 +0200 (MET DST)	[thread overview]
Message-ID: <199606192321.BAA10200@bolyai.cs.elte.hu> (raw)
In-Reply-To: <9606192116.AA29834@doc.physi.uni-heidelberg.de> from Achim Braemer at "Jun 19, 96 11:16:35 pm"

> 
> Erwin J. van Eijk writes on June 14:
>  > I have a slight problem with zsh-2.6Beta20 on OSF/1. The problem is,
>  > that if I widen an xterm window to, say, 130 chars, and I type a lot
>  > of stuff in it, after 80 chars the line is cleared, and the cursor
>  > goes to position 1 in the line. If you do a backspace, the
>  > cursor wraps to the previous line, and garbling everything. 

That problem should not occur with beta21.

> I have very similar symptoms on IRIX 5.2 with ZSH_VERSION
> 2.6-beta13. The problem is not easily reproduceable at all, it occurs
> after zsh has been running for a while. When I resize back to a width of
> 80 characters line editing is ok again. Now widen again and it breaks
> now immediately again.
> Very annoying.

Do not you use ncurses?  ncurses-1.9.8a had a bug which sometimes turned
off automargin in xterms.  This has a very similar effect.  This bug is
fixed in ncurses-1.9.9e.  The symphtomes are that when you write anything
to the screen which is longer than the width of the terminal the line will
not wrap (e.g. when you use cat to display a file lines longer than the
screen width will be truncated).

Zoltan



      parent reply	other threads:[~1996-06-19 23:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-14 12:45 Erwin J. van Eijk
1996-06-19 21:16 ` Achim Braemer
1996-06-19 21:25   ` Achim Braemer
1996-06-19 23:21   ` Zoltan Hidvegi [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=199606192321.BAA10200@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=braemer@doc.physi.uni-heidelberg.de \
    --cc=zsh-workers@math.gatech.edu \
    /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).