From: opk@thoth.u-net.com (Oliver Kiddle)
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: Problem with completion matching control
Date: Tue, 16 Feb 1999 01:14:37 +0000 [thread overview]
Message-ID: <199902160114.BAA03383@Indigo.thoth.u-net.com> (raw)
In-Reply-To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de> "Re: Problem with completion matching control" (Feb 15, 10:42am)
On Feb 15, 10:42am, Sven Wischnowsky wrote:
> As for the cursor position: I tried to make the completion code clever
> here by making it leave the cursor in the place where it is easiest to
> make the inserted line unambiguous. I know that this may look
> irritating but I think that this is the right thing to do. I could be
> convinced to make this controlled by an option, so that the cursor is
> left at the end if the option is unset.
I've done a few experiments and now agree with you that moving the
cursor back is better but I've also noticed something more subtle about
the behaviour which I think is a bug.
Starting with the usual:
zsh -f
compctl -M 'm:{a-z}={A-Z}'
:> temp > Temp
Now this behaves in a way that I like:
less t<tab><tab><tab>
But this behaves quite differently
less te<tab><tab><tab>
In the first case, the first tab completes 'temp', moves the cursor over
the e and lists 'Temp temp' below the line. The second tab capitalises
the T and moves the cursor to the end. The third tab then lowercases the
t and any more tabs will continue to cycle.
In the second case, the first tab completes to 'temp' and moves the
cursor over the e as before but it doesn't list anything below. Any
subsequent tabs do nothing.
In practical use, I tended to get the second scenario because I normally
press tab after typing more than one character. Anyway, it is certainly
the second case which I find annoying.
> Playing with this I also noticed that there is some weird interaction
> going on between inserting such a string and the setting of recexact
> (the exact inserted match isn't immediatly accepted, which is wrong if
> auto_menu is unset). I'll have a lokk at this.
I'm not sure if its the same as what you've noticed there. I get some
similar but different problems to what I described above when in the zsh
source directory after:
./co<tab><tab>
Here I again get no list and the menu completing stops at Config/ but
this is only with my options - its fine with zsh -f.
Thanks
Oliver Kiddle
next reply other threads:[~1999-02-16 1:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-16 1:14 Oliver Kiddle [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-24 8:39 Sven Wischnowsky
1999-02-23 10:04 Sven Wischnowsky
1999-02-24 5:11 ` Bart Schaefer
1999-02-22 23:35 Oliver Kiddle
1999-02-18 9:05 Sven Wischnowsky
1999-02-18 1:00 Oliver Kiddle
1999-02-17 8:00 Sven Wischnowsky
1999-02-16 13:58 Sven Wischnowsky
1999-02-16 17:04 ` Peter Stephenson
1999-02-16 8:30 Sven Wischnowsky
1999-02-15 9:42 Sven Wischnowsky
1999-02-14 19:35 Oliver Kiddle
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=199902160114.BAA03383@Indigo.thoth.u-net.com \
--to=opk@thoth.u-net.com \
--cc=wischnow@informatik.hu-berlin.de \
--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).