From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: gwing@primenet.com.au, zsh-workers@math.gatech.edu (zsh-workers)
Subject: Re: zle_refresh patch 2
Date: Wed, 5 Mar 1997 20:58:58 -0800 [thread overview]
Message-ID: <970305205858.ZM8212@candle.brasslantern.com> (raw)
In-Reply-To: gwing@primenet.com.au "Re: zle_refresh patch 2" (Mar 6, 2:56pm)
On Mar 6, 2:56pm, gwing@primenet.com.au wrote:
} Subject: Re: zle_refresh patch 2
}
} sorry, I haven't had much time up until now. I'm going to have to look at
} the way 3.1.* handles the Zle module before I can send a patch for all the
} problems - previously I've been sending patches to 3.0.*
I think you can continue patching 3.0.3-test4 as long as you don't make
reference to zle globals in non-zle .c files. Zoltan?
} The reason that the zle went into singlelinemode style when the terminal
} went down to 1 or 2 lines is because it was simpler. I seem to remember, it
} avoided *lots* of conditionals all the way through the code. I can change
} this and I would also probably have to change quite a bit of the prompt code
} to count number of lines, etc.
It was Peter's assertion that changing the value of "termok" was sufficient
to change zle into a sane state, without having to toggle the *ZLE options.
I tried this (see my most recent patch) and it seems to work OK; I'm just
worried that putprompt() or zleread() is going to call init_term() at a bad
time, and thus reset "termok" independently of lines/columns.
} There are a couple of choices here; when a terminal decreases number of
} lines to 1 or 2:
} 1) it goes into singlelinemode style (without setting SINGLE_LINE_ZLE)
} until the terminal increases its lines above 2.
This is fine as far as *I'm* concerned.
} There are also a couple of bugs which won't show up until the terminal goes
} down to < 5 or so columns. I think I kept getting destroyed memory structs
} so I didn't work out what buffers were being overflowed.
With `termok = TERM_BAD' in effect, I was able to set COLUMNS=2 without
any crashes. Of course, all I could ever see was the < and > that mean
that there's more text left and right of the visible screen, but I was
able to blind-type various commands and finally reset COLUMNS=80 with
no apparent ill effects.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
next prev parent reply other threads:[~1997-03-06 5:05 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
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 [this message]
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=970305205858.ZM8212@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=gwing@primenet.com.au \
--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).