mirror of
https://github.com/nushell/nushell.git
synced 2025-05-16 07:54:40 +02:00
## 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> |
||
---|---|---|
.. | ||
nu_plugin_custom_values | ||
nu_plugin_example | ||
nu_plugin_formats | ||
nu_plugin_gstat | ||
nu_plugin_inc | ||
nu_plugin_nu_example | ||
nu_plugin_polars | ||
nu_plugin_python | ||
nu_plugin_query | ||
nu_plugin_stress_internals | ||
nu-cli | ||
nu-cmd-base | ||
nu-cmd-extra | ||
nu-cmd-lang | ||
nu-cmd-plugin | ||
nu-color-config | ||
nu-command | ||
nu-derive-value | ||
nu-engine | ||
nu-explore | ||
nu-glob | ||
nu-json | ||
nu-lsp | ||
nu-parser | ||
nu-path | ||
nu-plugin | ||
nu-plugin-core | ||
nu-plugin-engine | ||
nu-plugin-protocol | ||
nu-plugin-test-support | ||
nu-pretty-hex | ||
nu-protocol | ||
nu-std | ||
nu-system | ||
nu-table | ||
nu-term-grid | ||
nu-test-support | ||
nu-utils | ||
nuon | ||
README.md |
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.