# Nushell core team meeting 2024-05-29
## Attendees
- devyn
- fdncred
- storm
- amtoine
- ian
- windsoilder
- woosaaahh
- kubouch
- andy

## Agenda
- [x] Release update - Any issues?
- [x] `path type` changes [broke zoxide](https://github.com/nushell/nushell/issues/12990). A PR has already been landed on the zoxide site to fix it.
- [x] `OSC 9;9` [bug](https://github.com/nushell/nushell/pull/12994) noticable with Windows Terminal, osc9_9 enabled and doing "Duplicate Tab"
- [x] Question on Discord `~/some/path/exe` can't be executed any longer. I got it to work with `^("~/.cargo/bin/eza" | path expand)` but that's kind of a pain.
- [x] Span ID refactor, step-wise: https://github.com/nushell/nushell/issues/12963
- [x] Step 1 ready: https://github.com/nushell/nushell/pull/12960
- [x] Should we revert the revert https://github.com/nushell/nushell/pull/12954? Looks like like YizhePKU baked the revert into [#12953](https://github.com/nushell/nushell/pull/12953).
- [x] Do we have `which` on Windows?
- yes
- someone reported that it doesn't work on Windows: https://discord.com/channels/601130461678272522/614593951969574961/1244916108671320074

## Discussed Topics

### Release topics
- `path type` - no biggy, not going to change it right now
- `ocs9;9` - not big enough to force a patch release
- `~/some/path/exe` should be executable - we need to investigate and do a patch release
- old behavior:
- `^"~/some_exe"` will expand `~` and run the expanded exe
- new behavior:
- `^"~/some_exe"` will not expand and runs exactly `~/some_exe`
- ^\`~/some_exe\` will expand `~`
- another workaround: `^("~/some_exe" | path expand)`
- Decision is to do a patch release after it's fixed
- Darren did a git bisect and it pointed the finger at https://github.com/nushell/nushell/pull/12921
- Not related to release #12985 eventually needs to be fixed. We can include it if we just happen to figure it out and fix it.

### Span ID Refactor

Start on the parser/AST side -> introduce the SpanID
Then whenever `Expression` gets used also use it to perform a lookup
At some point there will be some duplication.
Step by step migration moving over several types (with id, just id, bare span)

Devyn: churn with plugins, how can we ensure to minimize that: avoid renamings in public API as long as possible. So rather than renaming to `SpanWithId`, just add the `id` to `Span` (but also add `ActualSpan` as planned)

### 12953 (set_current_dir)

There's no need to revert the revert because YizhePKU added it in 12953. reedline needs to be updated before we land 12953. Jakub to respond in PR.

- [x] Leave note that reedline needs to be updated before merging

### `which` on Windows

Was actually an issue with `nur`, not Nushell

## free topic choice

### stream joining

Devyn wants a command that joins a stream with another stream coming from a closure (add to `append` and `prepend`)

"You only see streaming when nothing is happening and only then you see something so you see it's not streaming"

##### Design dilemma

How invisible can streams be.

"It just works" vs good introspection into the performance characteristics

- good debugging tools/infos for nerds
- label for streaming/collecting?
- dry-run mode
- use pipeline metadata to track if a collect occured in the pipeline, then which command collected?
- warning when collecting extreme amounts?

## Issues
> :bulb: the issues which [needs-core-team-attention](https://github.com/nushell/nushell/labels/needs-core-team-attention)

> :bulb: **Note**
> to list all the PRs currently [opened in `nushell/nushell`](https://github.com/nushell/nushell/pulls):
> ```nu
> gh pr list --json url,number,author,title
> | from json
> | each {|i|
> $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
> }
> | reverse
> | to text
> ```