# Nushell core team meeting 2025-01-15
## Attendees
- Darren
- Stefan
- Rose
- Ian
- Piepmatz
- Douglas
- Andy
- Michael
- Devyn
- Antoine
- Wind

## Agenda
- [x] [Rename `range` command to `slice`](https://github.com/nushell/nushell/pull/14825)
- [x] [Windows PWD per drive behavior](https://github.com/nushell/nushell/pull/14546)
- [x] [FilePermission type?](https://github.com/nushell/nushell/pull/14840)
- [x] [Aliasing modules](https://github.com/nushell/nushell/issues/14791).. solved?
## For next meeting
- [ ] Assignment statements or expressions
## Discussed Topics

### `range` cmd -> `slice` cmd
- Technical note: Deprecate as soon as replacement is around
- check the integrations if possible and send PRs

### PWD-per-drive-letter
- https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-getfullpathnamew -> windows sys call to expand relative paths takes per-drive working directory into account
- https://github.com/PowerShell/PowerShell/issues/17149 -> powershell doesn't set the system level working directory on `cd` so externals don't get the correct working directory for the non-current drive letter.
- Poll the community

### FilePermission
- File permissions and file modes should not be their own primitive type (`Value` cases are mostly settled at this point).
- Look into custom types as a follow up to allow custom behavior, display, etc. (Lua metatables as possible inspiration).

### aliasing modules and other symbols
- you can alias module members through reexport (h/t sid-6581)
- doesn't cover all cases like plugins or general subcommand renaming
- let's keep the issue open