Re: Style interactions (Re: zsh/complist and compinit)

[Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>]

Bart Schaefer wrote:

> On Feb 1,  5:11pm, Alexandre Duret-Lutz wrote:
> } Subject: Re: zsh/complist and compinit
> }
> } And by the way, since I am speaking of thing that
> } would help in the doc: I remember having spent
> } a lot of time to figure out that the group pattern
> } (of complist color definition) needed
> } group-name style to be set in order to work.
> 
> Yes, some indication of which styles depend on other styles would
> be nice in general.

I'd like to make the whole description more table-ish anyway. In the
descriptions of the styles things like `depends on', `see also'
together with plain lists of other styles (or styles and special
values for them) and in the description for functions tables of used
styles would be nice to have.

And examples, as you said... I just don't know which examples would be
good -- I mean we have people here who know better what would be
helpful because they needed some time to find it out.


While we are talking about styles anyway, I'd like to take the
opportunity to ask again: Peter, why does `remote_glob' use an
underscore instead of a `-'? Only historical reasons? Do you like that 
better? Does everyone except me like it better?

Bye
 Sven

diff -ru ../z.old/Doc/Zsh/compsys.yo Doc/Zsh/compsys.yo
--- ../z.old/Doc/Zsh/compsys.yo	Tue Feb  1 14:47:49 2000
+++ Doc/Zsh/compsys.yo	Wed Feb  2 10:41:28 2000
@@ -23,6 +23,12 @@
 ifnzman(noderef(Matching Control))
 for further details.
 
+Note also, that it is possible to use old completion definitions using 
+the tt(compctl) builtin command together with the functions for the
+new completion system. To enable this, the tt(_default) function from
+the tt(Base) directory of the distribution should be copied and
+modified as described in that file.
+
 startmenu()
 menu(Initialization)
 menu(Completion System Configuration)
@@ -71,7 +77,11 @@
 After initialization all the builtin completion widgets such as
 tt(expand-or-complete) will be redefined to use the new completion system.
 Should you need to, you can still bind keys to the old functions by putting
-a `tt(.)' in front, e.g. `tt(.expand-or-complete)'.
+a `tt(.)' in front, e.g. `tt(.expand-or-complete)'. Note that this
+means that the tt(zsh/complist) module has to be loaded before the
+completion system is initialized (i.e. the tt(compinit) function is
+called) to make sure that the tt(menu-select) widget defined by it
+will be redefined, too.
 
 subsect(Use of compinit)
 findex(compinit)
@@ -981,7 +991,13 @@
 If this style is set for the tt(default) tag, the strings in the value 
 are taken as specifications that are to be used everywhere. If it is
 set for other tags, the specifications are used only for matches of
-the type described by the tag.
+the type described by the tag. For this to work, the tt(group-name)
+style has to be set to an empty string. If the tt(group-name) tag
+specifies other names for the groups the matches in these groups can
+be colored by using these names together with the `tt((group)...)'
+syntax described for the tt(ZLS_COLORS) and tt(ZLS_COLOURS) parameters 
+and adding the specifications to the value for this style with the
+tt(default) tag.
 
 To be able to share the same specifications one has set up for the GNU
 version of the tt(ls) command one can use:

--
Sven Wischnowsky                         wischnow@xxxxxxxxxxxxxxxxxxxxxxx