zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk
Cc: Kyle Rose <krose@krose.org>
Subject: Re: Completion strangeness
Date: Thu, 19 May 2005 13:29:00 +0200	[thread overview]
Message-ID: <10766.1116502140@trentino.groupinfra.com> (raw)
In-Reply-To: <428A59D9.9050305@krose.org>

Kyle Rose wrote:
> This relates to zsh 4.2.5's ssh command line completion.  I don't know
> if this problem exists in earlier versions.

This is unrelated to the bug Bart pointed to. I can't reproduce what you
show exactly but I have isolated this down to what is undoubtably a bug.
Whether this is the problem you're having, I'm not sure.

>   krose@jihl ~% ssh krose@yupa..org
> 
> with the cursor over the second ".".

I always found that sort of stuff (filling in characters to the right of
the cursor) a bit weird. I've seen it before and assumed Sven meant it
as a feature. Maybe he didn't.

We can cut this down to a minimal setup to see problems:

zsh -f
autoload -U compinit; compinit
zstyle ':completion:*:::' _complete
_try() {       
compset -P '*@'
compadd -M 'r:|.=* r:|=*' \
        yupa-dmz.valley-of-wind.krose.org \
        yupa.krose.org yupa.valley-of-wind.krose.org
}
compdef _try t

Now compare the following:
% t y<tab>
  -> t yupa_
% t kr@y<tab>
  -> t kr@yupa_
% t kro@y<tab>
  -> t kro@yupa._.

Where _ is the cursor.

Patterns like '???' and '????' in compset also work. If compset has
removed four or more characters, we get the separator character (.)
inserted. So the problem is in the C code.

Oliver


       reply	other threads:[~2005-05-19 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <428A59D9.9050305@krose.org>
2005-05-19 11:29 ` Oliver Kiddle [this message]
2005-05-20  8:29   ` Bart Schaefer

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=10766.1116502140@trentino.groupinfra.com \
    --to=okiddle@yahoo.co.uk \
    --cc=krose@krose.org \
    --cc=zsh-workers@sunsite.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).