Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Per command _redirect completion
- X-seq: zsh-workers 16749
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Per command _redirect completion
- Date: Fri, 1 Mar 2002 05:47:23 +0000
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20020225094729.25283.qmail@xxxxxxxxxxxxxxxxxxxxxx> <20020226065605.35661.qmail@xxxxxxxxxxxxxxxxxxxxxxx> <15483.19190.263748.990476@xxxxxxxxxxxxxxxxxx> <15484.43079.6831.412868@xxxxxxxxxxxxxxxxxx> <20020228063522.62366.qmail@xxxxxxxxxxxxxxxxxxxxxxx> <15485.60818.216400.965143@xxxxxxxxxxxxxxxxxx>
On Feb 27, 10:35am, Sven Wischnowsky wrote:
}
} I wrote:
}
} > I would try to make compdef and parts of _normal (and probably
} > _complete) generic enough to use an assoc given as argument, so that
} > we get the pattern and services stuff.
I like this idea a lot, now that I've had a chance to digest it fully.
} - I wished there were an easier way than to use `${(e):-...}' in so
} many places. Sigh.
We'd need namerefs; ${(P)...} doesn't cut it for hashes. You could use
`eval' in a few places, I think, but not all of them.
On Feb 28, 9:42am, Sven Wischnowsky wrote:
}
} - Decide on a name for the concept so that we can give _do_type its
} final name and update the docs.
What if we called the function `_common'? It's use is both "commonplace"
and "shared" ...
} - Probably change the order of the strings given to _do_type (these
} are the strings used for lookup, e.g. command names for normal
} completion). These should be from most to least specific, I think.
That sounds sensible.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author