zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: <hzoli@VNET.IBM.COM> (Zoltan T. Hidvegi)
Cc: gwing@primenet.com.au, zsh-workers@math.gatech.edu
Subject: Re: zle_refresh patch 2
Date: Wed, 5 Mar 1997 13:55:59 -0800	[thread overview]
Message-ID: <970305135559.ZM7056@candle.brasslantern.com> (raw)
In-Reply-To: <hzoli@VNET.IBM.COM> (Zoltan T. Hidvegi) "Re: zle_refresh patch 2" (Mar  5,  3:56pm)

On Mar 5,  3:56pm,  (Zoltan T. Hidvegi) wrote:
} Subject: Re: zle_refresh patch 2
}
} Bart Schaefer wrote:
} > On Feb 3,  9:55pm, gwing@primenet.com.au wrote:
} > } Subject: zle_refresh patch 2
} > }
} > } It fixes coredumps and bad displays when terms are 1 or 2 lines.
} > } When a terminal is 1 or 2 lines high, the terminal will act as if
} > } SINGLE_LINE_ZLE is set.  This avoids many problems with the status line.
} >
} > There's already code that causes SINGLE_LINE_ZLE to become set if the
} > terminal starts out at, or is shrunk to, 1 line high or 1 column wide.
} 
} I'm not exactly sure that it is a good idea to explicitely set
} SINGLELINEZLE when the terminal shrinks to one or two lines.

Yes; I already agreed about that in response to a posting from Geoff on
Feb. 3.  The code is as it is now (and I changed it as I did in that
patch) because I didn't know about the meaning of "termok".  It would
be possible to replace all the fudging of SINGLELINEZLE and ZLE with
changes to "termok" -- at least, I think that's what PWS said at some
point.

} An other problem with Geoff's patch (whics is not a new problem, just this
} patch brought it up.  tsetcap only works in multiline mode, as it simply
} assumes that in single line mode termcap escapes are not available.  This
} means that some prompt escapes do not work in single line mode, which is
} especially annoying in print -P commands.  There should be a separate flag

I think "termok" is the right thing for that, too, but Peter or Geoff
should confirm.

} I'd really like to release zsh-3.0.3 ASAP, but these problems should be
} solved first.

I believe Geoff also said that there were some changes he needed to make
for very narrow terminals as well as very short ones.  Geoff?

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


  reply	other threads:[~1997-03-05 22:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-03 10:55 gwing
1997-02-03 18:05 ` Bart Schaefer
1997-02-03 18:34   ` gwing
1997-02-03 19:03     ` Bart Schaefer
1997-02-04  8:25     ` Peter Stephenson
1997-03-05 20:56   ` Zoltan T. Hidvegi
1997-03-05 21:55     ` Bart Schaefer [this message]
1997-03-05 23:06       ` Bart Schaefer
1997-03-05 23:47         ` Zoltan T. Hidvegi
1997-03-06  0:51           ` Bart Schaefer
1997-03-06  3:56             ` gwing
1997-03-06  4:58               ` Bart Schaefer
1997-03-06  5:03                 ` gwing
1997-03-06 18:32                   ` Zoltan T. Hidvegi
1997-03-06 18:58             ` Zoltan T. Hidvegi
1997-03-05 23:52 Zoltan T. Hidvegi

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=970305135559.ZM7056@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=gwing@primenet.com.au \
    --cc=hzoli@VNET.IBM.COM \
    --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).