From: Zefram <A.Main@dcs.warwick.ac.uk>
To: wayne@tenor.clarinet.com (Wayne Davison)
Subject: Re: Completion quirks
Date: Sat, 15 Jul 1995 03:19:33 +0100 (BST) [thread overview]
Message-ID: <515.199507150249@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <9507141749.aa19526@tenor.clarinet.com> from "Wayne Davison" at Jul 14, 95 05:49:42 pm
>My normal completion options have been to have "auto_list" set and nothing
>else. With this setup there has been a long-standing quirk that if you
>hit the completion key with a string that exactly matches a possible
>completion, zsh would choose that match even if other (longer) matches
>exist.
The REC_EXACT option does this. It would be helpful, when posting this
kind of query, for you to include a *complete* list of option
settings. Completion is affected by a great many options.
> Just today I installed hzoli10.1+ (including patch2) and its
>behavior is different but also wrong -- it chooses one of longer matches.
Curious. Setting REC_EXACT, I got the same behaviour. My non-hzoli beta10 plus lots of patches picks the right match, as does plain beta10.
[...]
>If I use zsh 2.6 beta10hzoli10.1+, it generates "ls ppmhist" -- the last
>item in the (unsorted) directory (I don't know if that's significant).
>If I hit tab a second it seems to try to treat it as a menu complete (even
>though it's not turned on), but fails to update correctly -- I get this:
>"ls ppmhist mhist".
>
>Turning on "menu_complete" in hzoli10.1+ behaves exactly the same way.
>
>Turning on "auto_menu" without menu_complete also fails, but in a
>different way: it displays "ls ppmhist " (no beep). One more tab beeps
>and backs up a space. Another tab displays "ls ppmhist .sh". Another
>tab displays "ls ppmhist mhist".
With hzoli10 I got this behaviour, and also with my own patched beta10
(though starting with the correct match). This problem is almost
certainly a result of my completion list patches (which I can't test
with every option, though I did give it a bit of a work out). Plain
beta10 for me misbehaved on the second completion, much in the way you
describe, so I think it is safe to say that REC_EXACT is, for the
moment, broken. I'll see what I can do...
-zefram
P.S. Can we expect an beta11-test release any time soon, Richard?
next prev parent reply other threads:[~1995-07-15 2:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-07-15 0:49 Wayne Davison
1995-07-15 2:19 ` Zefram [this message]
1995-07-15 3:54 ` about beta11 Richard Coleman
1995-07-15 4:53 ` Zefram
1995-07-15 6:28 ` Richard Coleman
1995-07-15 7:51 ` Zefram
[not found] <no.id>
1995-07-15 2:58 ` Completion quirks Zefram
1995-07-15 18:54 ` Wayne Davison
1995-07-17 19:20 ` Zoltan 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=515.199507150249@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=wayne@tenor.clarinet.com \
/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).