zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Zle display bug with LONG expansions
Date: Thu, 11 Jul 1996 15:18:02 -0700	[thread overview]
Message-ID: <960711151804.ZM9736@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: Zle display bug with LONG expansions" (Jul 11,  8:32pm)

On Jul 11,  8:32pm, Zoltan Hidvegi wrote:
} Subject: Re: Zle display bug with LONG expansions
}
} > In an 80x32 (or smaller?) xterm, do the following:
} > 
} > zagzig[38] echo **/*<TAB>
} 
} zle doen not handle the case when a line does not fit onto the screen.

Well, I know it doesn't handle it the way it does when a line does fit,
but it's obviously trying to do *something*.

} Geoff told me that for some reason zsh have to know in advance wether the
} current terminal automatically wraps the line.  He is probably right since
} some terminals start a new line when a character is printed in the last
} column while most terminals start a new line only is a character is printed
} after the last column.

Right; if zsh doesn't know about autowrap, and tries to print a newline
after the $COLUMNS'th character, you could end up with blank lines between
each two displayed lines.

But if zsh knows enough to avoid printing the newline because the terminal
autowraps, then it also ought to be able to avoid this.

Just mention it in etc/BUGS if nobody knows how to fix it ...

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"



  reply	other threads:[~1996-07-11 22:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-11 17:00 Bart Schaefer
1996-07-11 18:32 ` Zoltan Hidvegi
1996-07-11 22:18   ` Bart Schaefer [this message]
1996-07-12 11:40 Geoff Wing

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=960711151804.ZM9736@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=hzoli@cs.elte.hu \
    --cc=schaefer@nbn.com \
    --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).