From: Anthony Iano-Fletcher <Anthony.Iano-Fletcher@cbel.dcrt.nih.gov>
To: Zsh-workers@math.gatech.edu
Subject: Re: unique partial completion
Date: Mon, 2 Jun 1997 08:40:16 -0400 (EDT) [thread overview]
Message-ID: <199706021240.IAA17346@argo.dcrt.nih.gov> (raw)
In-Reply-To: <199705310810.EAA09857@hzoli.home> from "Zoltan Hidvegi" at May 31, 97 04:10:03 am
Hi
> The defaults have changed in zsh-3.1.1, the LIST_AMBIGUOUS option is on by
> default. Several other options are set now by default (see the Dec 27 1997
> entry in the ChangeLog). This should make zsh more user friendly when
> invoked without without any startup files.
> Just add unset LIST_AMBIGUOUS into your .zshrc.
Thanks, that seems to work for me. :-)
So far we have had 3 people who believe that the new default behaviour is not
entirely obvious. Why was this considered to make zsh more friendly?
Why doesnt LIST_AMBIGUOUS show up when I type 'setopt'? Its only when I
do 'unsetopt LIST_AMBIGUOUS' does "nolistambiguous" show up.
I looked for the Dec 27 1997 entry in the ChangeLog file but I
guess I'm behind the times. I did see an entry that says that setopt
was changed to show the non-default options. Is there a way of seeing
all the options set?
> Many people symply do not know about most of the zsh options.
Well that true for me.... I didnt spot this one although I did look - honest!
Anthony.
next prev parent reply other threads:[~1997-06-02 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-30 12:53 Anthony Iano-Fletcher
1997-05-30 16:15 ` Zefram
1997-05-30 16:52 ` Bart Schaefer
1997-05-30 17:07 ` Anthony Iano-Fletcher
1997-05-30 17:21 ` Geoff Wing
1997-05-30 17:36 ` Anthony Iano-Fletcher
1997-05-30 18:00 ` Vinnie Shelton
1997-05-31 8:10 ` Zoltan Hidvegi
1997-06-02 12:40 ` Anthony Iano-Fletcher [this message]
1997-06-02 16:37 ` Bart Schaefer
1997-06-02 20:41 ` Zoltan T. Hidvegi
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=199706021240.IAA17346@argo.dcrt.nih.gov \
--to=anthony.iano-fletcher@cbel.dcrt.nih.gov \
--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).