From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>,
zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Completion issues
Date: Sun, 2 Apr 2000 03:16:33 +0000 [thread overview]
Message-ID: <1000402031633.ZM17697@candle.brasslantern.com> (raw)
In-Reply-To: <E12bUTE-00011s-00.2000-04-01-21-26-12@mail12.svr.pol.co.uk>
On Apr 1, 9:26pm, Peter Stephenson wrote:
} Subject: Completion issues
}
} First, I hate the new behaviour of _complete_help. I use it to find out
} what context I'm in. Unfortunately I don't get to see that, because a huge
} list of style has scrolled by.
I won't say I *hate* the new behavior, but I was certainly alarmed by the
amount of style output that was generated even for something like "ls" or
"echo" that doesn't have any special handling. "cvs <^Xh>" is horrifying.
That list-colors, list-packed, list-rows-first, last-prompt, accept-exact,
and menu appear no less than 8 times each seems a tad excessive.
} I don't think a style to turn off styles in ^Xh is good enough,
} there's too much mucking around, and you may want the style information
} anyway. A workable alternative is that a numeric argument activates the
} style list --- this feature could be configurable by a style.
I like the numeric-argument idea. If we wanted to get really fancy, a
number from 1-4 could denote increasingly verbose output, so that using
universal-argument would produce the full-blown listing.
I'm not convinced we'd need a style to make that configurable, though.
It's pretty straightforward to create a zle widget that sets NUMERIC and
then calls another widget.
} Second, if I understood correctly, the default behaviour for completion is
} to ignore ignored completions completely. Thus the behaviour of $fignore
} has changed.
Unless I'm getting the wrong version of a function, it appears that this
is special-cased by _path_files so that $fignore has not changed -- but
if you use the ignored-patterns style instead, then ignored completions
really are ignored, and you need to add the _ignored completer to get
the old behavior back.
For the rest of the stuff you mentioned, I'm even more lost than you.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-02 3:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-01 20:26 Peter Stephenson
2000-04-02 3:16 ` Bart Schaefer [this message]
2000-04-03 12:56 Sven Wischnowsky
2000-04-03 13:11 Sven Wischnowsky
2000-04-03 15:25 Sven Wischnowsky
2000-04-05 18:30 ` Peter Stephenson
2000-04-04 9:49 Sven Wischnowsky
2000-04-06 7:31 Sven Wischnowsky
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=1000402031633.ZM17697@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=pws@pwstephenson.fsnet.co.uk \
--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).