extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-11-27 02:44:01 +01:00
Code Issues Packages Projects Releases Wiki Activity
d6df367c6b
nushell/crates/nu-engine/README.md
Waldir Pimenta 4bc9d9fd3b
Fix typos and capitalization of "Unicode" (#3234) 
* Capitalize "Unicode"

* Fix several typos

* Fix mixed whitespace in nu-parser's tests
2021-04-04 07:14:07 +12:00

1.3 KiB
Raw Blame History

Nu-Engine

Nu-engine handles most of the core logic of nushell. For example, engine handles: - Passing of data between commands - Evaluating a commands return values - Loading of user configurations

Top level introduction

The following topics shall give the reader a top level understanding how various topics are handled in nushell.

How are environment variables handled?

Environment variables (or short envs) are stored in the Scope of the EvaluationContext. That means that environment variables are scoped by default and we don't use std::env to store envs (but make exceptions where convenient).

Nushell handles environment variables and their lifetime the following:

  • At startup all existing environment variables are read and put into Scope. (Nushell reads existing environment variables platform independent by asking the Host. They will most likely come from std::env::*)
  • Envs can also be loaded from config files. Each loaded config produces a new ScopeFrame with the envs of the loaded config.
  • Nu-Script files and internal commands read and write env variables from / to the Scope. External scripts and binaries can't interact with the Scope. Therefore all env variables are read from the Scope and put into the external binaries environment-variables-memory area.