From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: Re: Completion services + xterm auto-margin revisited
Date: 22 Feb 2001 13:41:11 GMT [thread overview]
Message-ID: <slrn99a5nn.hfd.mason@coral.primenet.com.au> (raw)
In-Reply-To: <002a01c09ccd$04fbe660$21c9ca95@mow.siemens.ru>
Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru> typed:
:Well, it was a knowhow of Geoff (I still shudder when looking at refresh
:code).
It's commented. Well, the variables mostly are. And it understands
am (automargin) ... mostly. I've been taking a quick look at the
completion printing stuff. I presume the bits I should be looking
at are: Zle/complist.c:compprintfmt() and compprintlist()
Peter Stephenson <pws@csr.com> typed:
:By the way, completion listing for `typeset -' seems to tickle a relative
:of an ancient bug with xterm auto-margin: one of the possible descriptions
:is exactly 80 characters, but doesn't cause wraparound since there's
:nothing to follow, and redisplaying the command line happens one line too
:high.
I have some vague memory of a discussion yonks ago (different to the
one referenced above, I think) about whether a newline should be printed
at the end of any list or such (hereafter I'm just calling them lists
but also refer to other outputs) - one point here is that all lists need
to be considered to have an extra line if the last line extends to the
right margin, especially for any comparisons with ``lines'' (term height)
so the top doesn't unexpectedly scroll off. It's slightly ugly when the
list hits the bottom of the screen but I thought this happened. Maybe
a couple of cases were missed.
Point is: if the last output line is term width then you should always
be printing "\n" (*) and presume an extra line in the calculations.
(*) it's safest for 99.9% of used terminals whether or not they're
correctly reporting ``am'' capability (and if they're incorrectly
reporting it they'll have other problems anyway)
Regards,
--
Geoff Wing : <gcw@pobox.com>
Rxvt Stuff : <gcw@rxvt.org>
Zsh Stuff : <gcw@zsh.org>
next prev parent reply other threads:[~2001-02-22 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 12:02 Sven Wischnowsky
2001-02-22 12:14 ` Peter Stephenson
2001-02-22 12:43 ` Andrej Borsenkow
2001-02-22 13:41 ` Geoff Wing [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 13:02 Sven Wischnowsky
2001-02-22 13:01 Sven Wischnowsky
2001-02-22 11:49 Peter Stephenson
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=slrn99a5nn.hfd.mason@coral.primenet.com.au \
--to=mason@primenet.com.au \
--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).