Nushell 0.20: Command Enhancements, Breaking Changes, and Community Engagement

- The active shell in `shells` is [now more clearly shown](https://github.com/nushell/nushell/pull/2540) (gillespiecd) - `sleep` now [respects Ctrl+C](https://github.com/nushell/nushell/pull/2550) and can [pass along the output](https://github.com/nushell/nushell/pull/2558) (radekvit) - `str trim` and `trim` are [merged](https://github.com/nushell/nushell/pull/2576) (gillespiecd and radekvit) - `str find-replace` can now [global search/replace](https://github.com/nushell/nushell/pull/2569) (fdncred) - `open` now only streams for [non-files and large files](https://github.com/nushell/nushell/pull/2570) (sophiajt) - If supported on the platform, `benchmark` now gives [user/system/idle times as well](https://github.com/nushell/nushell/pull/2571) (radekvit) - Ctrl+D now [exits the current shell](https://github.com/nushell/nushell/pull/2583) (gillespiecd) - `fetch` now [supports CSV MIME types](https://github.com/nushell/nushell/pull/2587) (notryanb) ## Other improvements (fdncred, gillespiecd, lidin, andrasio, radekvit, sophiajt, coolshaurya) Removed unused dependencies, cleanups to duration, some ARM incompatibilities were fixed, some Ctrl+C issues were fixed, optimized some config reading, cleanup code in `get` and `nu-value-ext`, rustyline was upgraded (fixing a common instability in Windows), `help command` get some improvements, `random integer` got some stability fixes. # Breaking changes ## `in:` and `not-in:` are now `in` and `not-in` In working with operators, we've removed the colon from the `in` and `not-in` operators. ## `trim` and `str trim` are now just `str trim` We've merged the functionality and now just have the one `str trim` command. ## Locale-formatted numbers temporarily not supported As part of updating dependencies, we've had to temporarily disable locale-formatting numbers. We hope to fix this as dependencies update to the latest versions. ## Change in config location We've tried to use a supported 'directories' crate, which has meant having to change until we found a supported one. This, unfortunately, means that this release moves the config location again. On macOS, `config path` now points to: "$HOME/Library/Application Support/org.nushell.nu/config.toml", in 0.19.0 and earlier it was: "$HOME/Library/Preferences/org.nushell.nu/config.toml". # Zulip chat We're experimenting with using Zulip for our community chat and design discussions. If you want, you can [try the server and tell us what you think](https://nushell.zulipchat.com/). If you'd rather we stick with [Discord](https://discord.gg/NtAbbGn), you can tell us that, too :) # Looking forward We've put a [survey to get feedback from you about Nushell](https://docs.google.com/forms/d/e/1FAIpQLScEFzDh7j3jfAuVMBCQtQE-qfKAhugLCiUaaGL583QtGwz5fw/viewform?usp=sf_link). This will help us focus our efforts in the coming releases to refactor, trim, and polish Nu. Working with a large codebase is always a challenge, and recently we've been thinking through what features really make up the "core" Nu experience and what parts can be moved outside of Nu itself. This may mean making more things plugins, cutting back on the dependencies we use, and more. Getting your feedback makes sure we have a clear picture for what the "core" of Nu is to most people. Even if you're just curious about Nushell but aren't using it, we'd love to hear from you.

This section details various enhancements to Nushell 0.20, including improvements to `shells`, `sleep`, `str trim`, `str find-replace`, `open`, `benchmark`, Ctrl+D behavior, and `fetch`, along with general improvements such as dependency updates and stability fixes. It also outlines breaking changes like the removal of colons from `in` and `not-in`, merging `trim` into `str trim`, temporary removal of locale-formatted number support, and a config location change. The document introduces the use of Zulip for community chat and encourages users to provide feedback via a survey to help shape future development efforts.