Nushell core team meeting 2023-05-31

Attendees

• Stefan
• Storm
• Amtoine

Agenda

• cratification (move commands to nu-cmd-extra?)
  • nu-cmd-extra branch
  • the binary is working fine with the bits commands in nu-cmd-extra
  • now need to move on to getting the examples and tests to pass
• some fun: NES emulator as a plugin (from 0.44.0)
• We need to decide on the XDG_CONFIG_HOME PR once and for all. There's a lot of debate in the issue. We've had 2 polls, the latest isn't really overwelming newer_poll older_poll. I tend to think it'll be problematic if we provide an option to respect the XDG_CONFIG_HOME env var. I think we should either hard-code it to ~/.config or leave it like it is today. The biggest detractor, from a Windows perspective, to moving to ~/.config is that "Roaming User Profiles" won't work, which could be a big deal for Windows people who work on a Windows domain (WinDevOps, WinSysOps), but no one else cares about it (probably).
• Kubouch's performance concerns with PR9304 that fixed the drawing issues in PR and Issue 9264.
  • 1..5 | each { timeit { ls | table } } went from 3.9 to 6.4 ms
  • we shouldn't be cloning engine state in table
• Cool stuff - 1Kinoti making nu script into rust with his new Option and Result https://github.com/1Kinoti/stdx.nu
• package manager

Discussed Topics

cratification

@storm is doing the work with the bits commands, making sure it's all working fine.
the goal being to get a structure for other people to jump in and contribute!

• bits commands => in progress
• bytes and maths commands => todo
• 100% / 0% commands => todo

@storm tries to complete the bits commands by the week-end and we try to ship it just before the release

package manager

it's a work in progress in nushell/nupm.
we've decided to merge amtoine/nupm, kubouch/nuun and nupac/nupac together and we are working on a design document right now?

triage

not so much done but some points in the triage document to look at

XDG PR

we're looking for people with strong opinions to decide

In the new poll there was some interest in directly changing the default config location to just ~/.config but this would be a strong breaking change. (but reflects the spec that is very linux focussed)

A compromise that would break less users right now would be to keep the current default but respect the $XDG_CONFIG_HOME (which is very likely unset if you were to use nushell as a login shell??)

performance concern

we need you @kubouch

PR's

gh pr list --json url,number,author,title
| from json
| each {|i|
    $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
}
| reverse
| to text