From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@math.gatech.edu
Subject: Re: autolist?
Date: Wed, 27 May 1998 07:49:42 +0200 (MET DST) [thread overview]
Message-ID: <199805270549.HAA11050@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: acs@alumni.princeton.edu's message of Wed, 27 May 1998 00:34:40 -0400
acs@alumni.princeton.edu wrote:
>
> Ever since I upgraded to 3.1.3, I've had problems with autolist.
> Here's an example:
>
> ...
>
> And then I must press <TAB> again in order to get the list to
> appear:
>
> mithril% ls -d /usr/local/src/zsh-3.<TAB>
> zsh-3.0.5 zsh-3.1.3
> mithril% ls -d /usr/local/src/zsh-3.
>
>
> How do I get the old 3.0.5 behavior back?
>
unsetopt listambiguous # Grrr.
(That's the other completion-option now set by default.)
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
reply other threads:[~1998-05-27 5:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199805270549.HAA11050@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@math.gatech.edu \
/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).