Some interoperability suggestions #14355
PegasusPlusUS
started this conversation in
Ideas
Replies: 3 comments 5 replies
-
The first 2 can be handled with aliases like you mentioned. It's easy enough to place those in your config.nu file. I'm not on a Windows system today but number 3 looks familiar. Can you explain more about what it's doing and what you want nushell to do? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Beta Was this translation helpful? Give feedback.
3 replies
-
Complete PWD per drive support for nushell, will send PR after testing several days. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm a new user of Nushell. I found some interoperability and user-friendly improvement potentials:
Consider supporting dir (GitHub Codespaces bash supports it, and PowerShell supports dir/ls).
When users try to use cat or type, they encounter error messages. Providing an alias for open might be better, or at least mentioning open in the current error message.
On Windows, currently, if using a drive letter, only absolute paths are allowed. However, Windows natively supports the "current directory" concept for each drive. I hope Nushell can also accept paths like C: or D:test.
Beta Was this translation helpful? Give feedback.
All reactions