zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Completion strangeness
Date: Fri, 20 May 2005 08:29:45 +0000	[thread overview]
Message-ID: <1050520082945.ZM6616@candle.brasslantern.com> (raw)
In-Reply-To: <10766.1116502140@trentino.groupinfra.com>

On May 19,  1:29pm, Oliver Kiddle wrote:
} Subject: Re: Completion strangeness
}
} This is unrelated to the bug Bart pointed to.

I was about to say, "then I was mistaken."

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

[snip]

} 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.

I fiddled with this just a little.  It's not always "four or more" --
it's somehow related to the length of the (un?)ambiguous prefix in the
part compset leaves behind.  For example, if you change
	yupa-dmz.valley-of-wind.krose.org
to
	yuppa-dmz.valley-of-wind.krose.org
in your minimal example (extra 'p'), then the problem appears only
after compset has removed five or more characters.  If you change the
set of completions to
	yupa-dmz.valley-of-wind.krose.org \ 
	yipa.krose.org yopa.valley-of-wind.krose.org
then the problem appears only after seven or more characters are
removed.  And you can see it with

% t 123456@y

so it's not related to "kro" forming a substring of the right side.


      reply	other threads:[~2005-05-20  8:30 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
2005-05-20  8:29   ` Bart Schaefer [this message]

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=1050520082945.ZM6616@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).