mirror of
https://github.com/nushell/nushell.git
synced 2025-06-01 07:35:49 +02:00
273226d666
## Description - Fixes #12891 - An escape for #12835 Currently, Nushell is not very friendly to Python workflow, because Python developers very often need to activate a virtual environment, and in some workflow, the _activate.nu_ script is not near to "current working directory" (especially ones who use [virtualenvwrapper](https://virtualenvwrapper.readthedocs.io/en/latest/) and [Poetry](https://python-poetry.org/)), and hence, is not auto-completed for `overlay use`. Though Nu v0.102.0 has improved auto-complete for `overlay use`, it doesn't work if user starts the file path with `~` or `/`, like: ```nu > overlay use /h ``` ```nu > overlay use ~/W ``` ### Before:  ### After:   ## User-Facing Changes No ## Tests + Formatting Passed --------- Co-authored-by: blindfs <blindfs19@gmail.com>
Nushell core libraries and plugins
These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.
Foundational libraries are split into two kinds of crates:
- Core crates - those crates that work together to build the Nushell language engine
- Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.
Plugins are likewise also split into two types:
- Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
- Extra plugins - these plugins run a wide range of different capabilities like working with different file types, charting, viewing binary data, and more.