zsh-workers
 help / color / mirror / code / Atom feed
From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
To: Oliver Kiddle <opk@u.genie.co.uk>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: zsh 4.x bug in completion?
Date: Tue, 10 Jul 2001 09:24:16 +0400 (MSD)	[thread overview]
Message-ID: <Pine.SV4.4.33.0107100922120.22525-100000@itsrm2.mow.siemens.ru> (raw)
In-Reply-To: <3B4A069B.97E6B4F1@u.genie.co.uk>

On Mon, 9 Jul 2001, Oliver Kiddle wrote:

> Peter Stephenson wrote:
> >
> > There's a list of `possible incompatibilities' in the README.  It would be
> > good if you could list any others you found.  I'm sure there must be more
> > I've forgotten about.
>
> Before we start listing this as a known incompatibility, I should just
> point out that I can't reproduce this "bug". This may be something to do
> with vi/emacs keybindings and how you move the cursor to the `e' of
> echo. I can't think of much else seeing as the example starts from zsh
> -f. Can anyone else reproduce it?
>

Yes, I can with slightly outdated CVS. Using new completion and _prefix
completer I do not even get autoremoved space added (unless add-space is
set).

I won't claim it is neccessarily a bug. But I never used prefix completion
myself so I'm not sure what is correct (=logical?) behaviour.

-andrej


  reply	other threads:[~2001-07-10  5:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09 18:33 Stefan `Sec` Zehl
2001-07-09 18:49 ` Andrej Borsenkow
2001-07-09 18:54 ` Peter Stephenson
2001-07-09 19:31   ` Oliver Kiddle
2001-07-10  5:24     ` Andrej Borsenkow [this message]
2001-07-10  8:10       ` Bart Schaefer
2001-07-10  9:19         ` Sven Wischnowsky
2001-07-10  9:32           ` Peter Stephenson
2001-07-10 16:33             ` Bart Schaefer
2001-07-11  8:20               ` Sven Wischnowsky
2001-07-10  5:54     ` Thomas Köhler

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=Pine.SV4.4.33.0107100922120.22525-100000@itsrm2.mow.siemens.ru \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=opk@u.genie.co.uk \
    --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).