# Nushell core team meeting 2024-01-31
## Attendees
- storm
- sophia
- darren
- jakub
- ian
- edhowland
- antoine

## Agenda
- [x] Nupm documentation command and style: see [nupm#60](<https://github.com/nushell/nupm/pull/60>) and a [sample style from NGM](<https://github.com/amtoine/nu-git-manager/blob/main/docs/index.md>) generated with [`doc` in `toolkit.nu`](<https://github.com/amtoine/nu-git-manager/blob/main/toolkit.nu#L332>)
- [x] `glob` as `const`? see [#11639](<https://github.com/nushell/nushell/pull/11639>) also raises the question of `path expand` and `path exists` as `const`
- [x] Background jobs [#11696](https://github.com/nushell/nushell/pull/11696)
- [x] Redirection: redirection destination not available for commands
- [x] Not sure background jobs should be coupled to Reedline ?
- [x] Explanation of the functionality of the *external_printer* in Reedline [#737](https://github.com/nushell/reedline/pull/737)
- [x] Ability to send data to Crossbeam channels
- [x] To me it would be cleaner if the output could also be directed to a file
- [x] Then you would not have to involve the painter
- [x] Similar to the way EnvLogger has the ability to output to a file
- [x] Quick dataframe update
- [x] There have been lots of changes in reedline and nushell recently. If you're not running on the latest main, now is the time to do so since we're close to a new release. It would also be good for everyone to do `alias mv = umv` since we landed the `umv` command (uutils).

## Discussed Topics

- docs
- Let's start somewhere and figure out what we like and what we don't like.
- It would be good to have Examples supported properly in custom commands.
- Sophia suggested something maybe like `# [example] foo bar 1 2 3` as a lightweight way to add examples where they can be scraped.
- Maybe examples and test annotations are related so once we implement annotations we can hit both.
- glob - closed so no big deal, `ansi` is `const` now, `path exists` is probably ok now
- background job - should we have a parameter to capture the output of bkgrnd jobs. Maybe redirect by default so we're not getting spew into the shell itself. And maybe treat that as another stdout and later output that to a file.
- should external printer even exist in reedline at all?
- Sohpia's description about registring to receive output from external_printer so you can be notified that something has "finished".
- external_printer - storm to work with ian via the issue
- dataframe - Sophia arrow-rs vs polars-arrow, the datatypes are just enough different to make our lives difficult. Like Arc vs Box in certain types.
- dataframes should be unstable until we can figure out a way forward
## 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
> ```