mirror of
https://github.com/nushell/nushell.git
synced 2025-01-23 06:39:17 +01:00
cc5c4d38bb
* Expand path when converting value -> PathBuf Also includes Tagged<PathBuf>. Fixes #3605 * Expand path for PATH env. variable Fixes #1834 * Remove leftover Cows after nu-path refactor There were some unnecessary Cow conversions leftover from the old nu-path implementation. * Use canonicalize in source command; Improve errors Previously, `source` used `expand_path()` which does not follow symlinks. As a follow up, I improved the source error messages so they now tell why the source file could not be canonicalized or read into string. |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| Cargo.toml | ||
| README.md | ||
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 theHost. They will most likely come fromstd::env::*) - Envs can also be loaded from config files. Each loaded config produces a new
ScopeFramewith 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 theScope. Therefore all env variables are read from theScopeand put into the external binaries environment-variables-memory area.