From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers <zsh-workers@sunsite.auc.dk>
Subject: Re: Problem with setting both listpacked&listrowsfirst?
Date: Sat, 25 Sep 1999 22:07:51 +0000 [thread overview]
Message-ID: <990925220752.ZM2123@candle.brasslantern.com> (raw)
In-Reply-To: <19990924063116.21058.rocketmail@web1304.mail.yahoo.com>
On Sep 23, 11:31pm, Felix Rosencrantz wrote:
} Subject: Problem with setting both listpacked&listrowsfirst?
}
} I think I've applied all the completion patches to ZSH 3.1.6-pws-5.
} (7959 7960 7974 7985 7998 8011 8021 8028)
}
} When I do a "setopt listpacked listrowsfirst" and attempt completion
} with tab I don't get a listing for ambiguous matches.
I can reproduce this, but ONLY if using the new-style completions, and
then (so far) only for normal file completions (e.g. completion after
"ls"). It's got something to do with lines 8880-8919 of zle_tricky.c,
and how the value of `i' is computed (Sven, I know it's going to be two
weeks until you read this, but: I thought you were going to start using
more descriptive variable names?).
I tried a few different tweaks, but although I got it to display the list
I couldn't get it to position the cursor properly afterwards.
I can't figure out how to get zsh to enter the branch at 8826-8856, so
I don't know whether that has a problem as well.
Even for completions that do work, the columns are ragged:
zagzig<4> set<TAB>
set setclock setconsole setenv setfdprm setfont
setfx setkeycodes setleds setmetamode setopt setserial
setsid setsysfont setterm setup setup_compinit setxkbmap
I don't know of that's an intended side-effect of LISTPACKED or not, but
it doesn't always happen.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-09-25 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-24 6:31 Felix Rosencrantz
1999-09-25 22:07 ` Bart Schaefer [this message]
1999-10-12 7:19 Sven Wischnowsky
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=990925220752.ZM2123@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).