From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Problem with completion matching control
Date: Thu, 18 Feb 1999 10:05:47 +0100 (MET) [thread overview]
Message-ID: <199902180905.KAA06868@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: opk@thoth.u-net.com's message of Thu, 18 Feb 1999 01:00:01 +0000
Oliver Kiddle wrote:
> On Feb 16, 9:30am, Sven Wischnowsky wrote:
>
> > I can't reproduce it, can you give me information about the completion
> > options you have set or unset and any compctl's used here (global
> > matchers, default completion, special completion for the command,...).
>
> It was from zsh -f so with all the default options and (lack of)
> completions. Only the one matching completion I mentioned. It also
> occurs with my setup; my options are:
>
> setopt -09ghJOPRTX +16I setopt AUTO_PARAM_KEYS setopt AUTO_REMOVE_SLASH
> setopt COMPLETE_IN_WORD setopt EQUALS setopt EXTENDED_GLOB setopt
> EXTENDED_HISTORY setopt GLOB_COMPLETE setopt HIST_NO_STORE setopt
> LIST_AMBIGUOUS setopt LIST_BEEP setopt MULTIOS setopt POSIX_BUILTINS
Hm, still can't reproduce this. Do you still get the behavior (for the
other: completion after `t' and `te' behaved differently) with all
recent patches: the completion option cleanup from 5399 with it's
followup 5407 and the patch I sent yesterday in 5412?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-02-18 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-18 9:05 Sven Wischnowsky [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 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-16 1:14 Oliver Kiddle
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=199902180905.KAA06868@beta.informatik.hu-berlin.de \
--to=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).