[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-bash] Help to add new builtin
From: |
Joaquin Manuel Crespo |
Subject: |
Re: [Help-bash] Help to add new builtin |
Date: |
Thu, 8 Aug 2019 10:09:33 -0300 |
Thank you a lot for the tip.
One question, since "enable" load the program as a builtin into bash
(excluding that in builtin the same is executed in the same ram space as
the shell and by the shell) in this case, What is the advantage of use
"enable" instead of execute the program in another child PID putting the
program in the "PATH" variable? Regardless the minimal difference of speed.
I would like integrate my programs directly into the source code, instead
of storage in another folder the programs or/and put the "enable" builtin
in "/etc/bash.bashrc"
El jue., 8 de ago. de 2019 a la(s) 09:47, Greg Wooledge (address@hidden)
escribiĆ³:
> On Thu, Aug 08, 2019 at 08:19:50AM -0300, Joaquin Manuel Crespo wrote:
> > I have a personal project ( ProyectoInvierno
> > <https://www.github.com/shyanjmc/ProyectoInvierno> ) and I am trying to
> add
> > a new builtin to BASH.
>
> For some time, bash has had the ability to create and use "loadable
> builtins", which are stored in separate files on disk, and loaded with
> the "enable" command (enable -f filename builtinname).
>
> You might want to pursue that, instead of trying to alter the source
> code of bash itself, unless you project actually is "to get my builtin
> into the worldwide bash releases".
>
--
Un cordial saludo.
*JoaquĆn Manuel Crespo.*
Gnu/Linux SysAdmin / C developper