Darren Schroeder

this seems to work ``` > ls \\localhost\admin$ ╭─────┬──────────────────────────────────────────────────────────────────┬──────┬──────────┬────────────────╮ │ # │ name │ type │ size │ modified │ ├─────┼──────────────────────────────────────────────────────────────────┼──────┼──────────┼────────────────┤ │ 0 │ \\localhost\admin$\AppReadiness │ dir │ 0 B...

I think this is the problem. Our glob crate doesn't know what to do with VerbatimUNC paths. https://github.com/nushell/nushell/blob/6e69d40bb9f5602cf110e75c3cdd27be9d1d15ca/crates/nu-glob/src/lib.rs#L226-L239 unc path ``` root=[Some("\\\\?\\UNC\\localhost\\admin$\\")] ``` path components ``` p=PrefixComponent { raw: "\\\\?\\UNC\\localhost\\admin$",...

`cd` is not the same as `ls`, of course, but this problem could be related. we use dunce as well but switching from dunce to crate x may not solve...

i'm guessing they're related but someone would have look at the ls code and debug it probably.

@ehawman That's weird. Those look like dotnet errors. nushell doesn't have any dotnet but on Windows it may call into the Windows API that is dotnet.

ya, mine is like ~700 lines long. this seems reasonable but I'd like to relocate it to the `docs\sample_config` folder where it needs to be anyway (some !include_str code may...

i tend to put the source/use right before they're used. semi-related to this is another feature we'd love to have at some point, which is a `nu-fmt` program to format...

@jmoore34 we really need to add the `lib_dirs` functionality from 0.44 prior to our 0.60 release. this will enable us to put folder in that variable and, from any directory,...

@fgimian there are several commands that do not support dynamic paths like `use` and `source`. That's actually what the help message is intended to convey. Perhaps we should be more...

nushell currently does not allow you to source with dynamic paths https://www.nushell.sh/book/thinking_in_nu.html