Wind 1e051e573d
fix $env.FILE_PWD and $env.CURRENT_FILE inside use (#14101)
# Description
Fixes: https://github.com/nushell/nushell/issues/13425

It's just a follow up to #13958.

User input can be a directory, in this case, we need to use the return
value of `find_in_dirs_env` carefully, so in case, I renamed
maybe_file_path to maybe_file_path_or_dir to emphasize it.


# User-Facing Changes
`$env.FILE_PWD` and `$env.CURRENT_FILE` will be more reliable to use.

# Tests + Formatting
Added 2 tests
2024-11-05 14:12:01 +08:00
..
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:14:11 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2024-10-20 23:12:41 +02:00
2022-02-07 14:54:06 -05:00

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.