Re: PATCH: completion

["Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>]

On Oct 27, 10:42am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: completion
}
} No, the output of `functions' isn't changed (of course).

Oh, I thought you said it was.  You meant the value of $functions, then?
That's not so bad, but you could still get unexpected effects.

} > } If you load the parameter module in your `.zshrc', you'll notice that
} > } `compinit' now loads `parameter' and `zleparameter'. Without `compgen' 
} > } we need it in too many places to get away without it.  And now the same 
} > } question as for the `computil' module: should we make them be
} > } automatically autoloaded (and linked in for static shells)
} > 
} > Yes!  If the stock set of completion functions are useless without them,
} > they have to be linked into static shells.  However, it would be nice if
} > they weren't actually "loaded" in the zmodload sense until they were
} > needed, even in a static shell.  That's going to require some changes to
} > the way zmodload and static modules work.
} 
} Right. Hadn't thought about that either. But in a fully static shell,
} wouldn't it a bit surprising when, for example, parameters just appear 
} because they are used (because they were `autoloaded')?

That's what I meant about "require some changes to the way zmodload and
static modules work."  Basically, I want the modules linked in, but not
initialized until an actual "zmodload" is attempted on them.  This is
not the same as the current auto-autoloading.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com