On 12/14/18 3:01 PM, Peng Yu wrote:
>> I suppose the first thing needed to make that work, and maybe the only
>> thing needed to make that work, is agreement on the name of a search path
>> environment variable that enable can use to find loadable builtins.
>
> Why not just use an environment vari
> I suppose the first thing needed to make that work, and maybe the only
> thing needed to make that work, is agreement on the name of a search path
> environment variable that enable can use to find loadable builtins.
Why not just use an environment variable such as LOADABLES_PATH (just
like the
On 16 Jul 2015 14:53, Chet Ramey wrote:
> On 7/14/15 5:11 AM, Mike Frysinger wrote:
> > On 14 Jul 2015 11:35, Pierre Gaston wrote:
> >> I think adoption would be difficult considering even a useful loadable
> >> builtin like "finfo" has not found its way into default installations, b
> ut
> >> for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/15 5:11 AM, Mike Frysinger wrote:
> On 14 Jul 2015 11:35, Pierre Gaston wrote:
>> I think adoption would be difficult considering even a useful loadable
>> builtin like "finfo" has not found its way into default installations, b
ut
>> for insta
On 14 Jul 2015 11:35, Pierre Gaston wrote:
> I think adoption would be difficult considering even a useful loadable
> builtin like "finfo" has not found its way into default installations, but
> for instance I can imagine bash programmable completion could go another
> level with an embedded interp
