4 ms·
Current shells include [lots of builtins](https://www.unix.com/man-page/freebsd/1/builtin/ https://www.unix.com/man-page/freebsd/1/builtin/), I don't think incl
by llimllib 3y ago
Current shells include [lots of builtins](https://www.unix.com/man-page/freebsd/1/builtin/ https://www.unix.com/man-page/freebsd/1/builtin/), I don't think including a `cp` or `mv` that fits a shell with a different style is that different
- mongol 3y agoGood point. I wonder if there was some criteria that determined if a utility were to be a command or a builtin, originally. I thought a shell first and foremost was about working with processes, and a little less about working with files. But both are obviously needed, one way or another, so will be interesting to see what becomes of this.
- forgotpwd16 3y agoBased on list seems builtin functionality is what is used to work with processes (nohup, kill, etc), environment (where, which, etc), and for shell as programming language ([, while, etc).
- mongol 3y agoYes. As an example, the source builtin would not be possible to implement as a command as a child process can't change its parent's environment. So those types of concerns play in I think.