zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Anthony Iano-Fletcher <Anthony.Iano-Fletcher@cbel.dcrt.nih.gov>,
	Zsh-workers@math.gatech.edu
Subject: Re: unique partial completion
Date: Mon, 2 Jun 1997 09:37:46 -0700	[thread overview]
Message-ID: <970602093746.ZM14926@candle.brasslantern.com> (raw)
In-Reply-To: <199706021240.IAA17346@argo.dcrt.nih.gov>

On Jun 2,  8:40am, Anthony Iano-Fletcher wrote:
} Subject: Re: unique partial completion
}
} > 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?

I don't think the problem is with listambiguous, I think it's with listbeep.
I'm not sure, as I don't have 3.1.x compiled ... is listbeep no longer a
default setting?  Or is it broken?

} Is there a way of seeing all the options set?

setopt kshoptionprint.  I started doing that long ago; there probably ought
to be a command-line switch for setopt to turn it on just for one pass.

As long as I'm on the subject, there also ought to be a switch to list all
the options in "positive" form, e.g. so you get

listambiguous off

instead of

nolistambiguous on

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts        http://www.nbn.com/people/lantern


  reply	other threads:[~1997-06-02 16:44 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
1997-06-02 16:37     ` Bart Schaefer [this message]
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=970602093746.ZM14926@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=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).