# Nushell core team meeting 2024-10-09
## Attendees
- Jack
- Ian
- Stefan
- Michael
- Devyn
- Doug
- Piepmatz
- Andy
- Antoine
- Darren

## Agenda
- [x] [14022](https://github.com/nushell/nushell/issues/14022) - We should try and figure out some type of solution. If you're on Windows and you have a tool that wants to shell out run something and the tool quotes a full path to a binary, it will fail because double quotes interpret escapes.

https://www.nushell.sh/book/working_with_strings.html

Some options/ideas from core-team discord chat
- intercepting a path and escaping every `\`
- intercepting a path and changing every `\` to `/` since slashes work on windows too
- Remove escapes altogether from `""` instead use `$"(char nl)"`
- What if we escape only special characters, as outlined in [this](https://stackoverflow.com/questions/19176024/how-to-escape-special-characters-in-building-a-json-string/27516892#27516892) - not sure it would work though
- Decide which is more important for nushell (A) Being 100% JSON superset (B) Being more Windows-friendly

Some Usage Stats

❯ get_all_nu_downloads "0.98.0"
╭─#─┬─────source─────┬─downloads─╮
│ 0 │ github         │     13310 │
│ 1 │     gh_apple   │       645 │
│ 2 │     gh_linux   │      5688 │
│ 3 │     gh_windows │      6977 │
│ 4 │ brew           │      2757 │
│ 5 │ cargo          │      3076 │
╰─#─┴─────source─────┴─downloads─╯

- [ ] Should we accept [this vulnerability report]( https://github.com/nushell/nushell/security/advisories/GHSA-hrj7-3qr6-j97m) or is it, like was mentioned in core-team, just the way windows works?
- [ ] A handful+ of PRs that need to be review and potentially landed before the release.

## Discussed Topics