From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: zsh-workers <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: cursor position after completion
Date: Tue, 14 Sep 1999 22:28:38 -0700 (PDT) [thread overview]
Message-ID: <19990915052838.5059.rocketmail@web1301.mail.yahoo.com> (raw)
I would like to request a different solution to cursor positioning with
completion and matching control.
When I'm completing filenames where matching control occurs, I'd prefer
the cursor to move to the position of the first place where characters
are missing, not the last. If I'm completing something that might be
an option I would like to have it put me in the last position.
So to me the questions are:
How should ZSH decide at which matching hot spot to leave the cursor?
If it makes the wrong choice, is there a better way for the user to
correct the position and continue completing?
It seems that there should be a more intuitive solution. I think there
are alternatives to counting matches.
Maybe a simple mechanism that would allow the user to cycle the
cursor through the matching hot spots of a word. Maybe before menu
completion kicks in the cursor could be moved to the different hot
spots. Though this might be annoying, too.
Maybe it would it be useful if there was a parameter to configure if you
prefer the cursor to be positioned at the first or last hot spot.
Or maybe the matching control specifications could be enhanced with cursor
positioning rules.
One problem with matching control is that it can leave the cursor deserted
at a position that doesn't allow you to make the choice you want to
make. For example
% mkdir /tmp/test
% cd /tmp/test
% touch zsh3.1.6-pws-3 zsh3.1.6-test-3 zsh3.1.6-test-3_debug
% compctl -M 'r:|[.,_-]=*'
% more zsh[] #Hit TAB and you get:
% more zsh3.1.6--3[]
But if you wanted the zsh3.1.6-pws-3 you have to move the cursor up to the
position between the minus signs.
I guess I just want it to dwim. One of the reasons, I moved from tcsh to zsh,
is that zsh does matching control, that handles partial completion &
case-sensitivity issues so much better. But this new behavior doesn't feel
quite right.
-FR.
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
next reply other threads:[~1999-09-15 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-15 5:28 Felix Rosencrantz [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-15 8:18 Sven Wischnowsky
1999-09-02 11:06 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=19990915052838.5059.rocketmail@web1301.mail.yahoo.com \
--to=f_rosencrantz@yahoo.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).